oceanbase-deploy@2.0.3
VERIFIED· install onlyPublisher claims: "Route community and commercial distributed OceanBase deployment and operations through obd. Use for general or multi-domain OceanBase/obd requests, product-form discovery, or when the correct specialized skill is unclear. Route concrete work to cluster management, OBD administration, tenant management, testing, or diagnostics." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-07 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
description: Install, update, and administer the OBD controller, including mirrors and repositories, offline artifacts, stored-credential encryption, dynamic tools, top-level host utilities, trace eviFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.- Developer mode can expose hidden commands, accept undefined options, or weaken validation. Enable it only for an explicit development workflow with a reviewed reason and stop condition; restore it aFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Do not apply a controller-wide root or sudo eligibility gate. An existing OBD may be inspected and used under its owning login-session user for every operation that user can perform. Evaluate privilegFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.| Explicitly inspect or change `obd env`, developer mode, lock behavior, automatic confirmation, transfer behavior, or telemetry | [runtime-environment.md](references/runtime-environment.md) |Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- Developer mode can expose hidden commands, accept undefined options, or weaken validation. Enable it only for an explicit development workflow with a reviewed reason and stop condition; restore it aFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.- `obd env` subcommands can be hidden from ordinary help in some builds. Prove the exact command and value semantics from the installed build or version-matched documentation before invoking it; do noFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.Treat `obd env` values and developer mode as persistent controller-wide policy. They can change later commands for every deployment and user of the same OBD home. Read-only inspection should stay limiFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.Use this reference only when the user explicitly asks to inspect or change `obd env`, developer mode, lock behavior, transfer behavior, or telemetry, or when concrete failure evidence identifies one oFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.Use this reference only when the user explicitly asks to inspect or change `obd env`, developer mode, lock behavior, transfer behavior, or telemetry, or when concrete failure evidence identifies one oFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.| Explicitly inspect or change `obd env`, developer mode, lock behavior, automatic confirmation, transfer behavior, or telemetry | [runtime-environment.md](references/runtime-environment.md) |Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.Treat `obd env` values and developer mode as persistent controller-wide policy. They can change later commands for every deployment and user of the same OBD home. Read-only inspection should stay limiFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- `obd env` subcommands can be hidden from ordinary help in some builds. Prove the exact command and value semantics from the installed build or version-matched documentation before invoking it; do noFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.description: Install, update, and administer the OBD controller, including mirrors and repositories, offline artifacts, stored-credential encryption, dynamic tools, top-level host utilities, trace eviFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- `obd env` subcommands can be hidden from ordinary help in some builds. Prove the exact command and value semantics from the installed build or version-matched documentation before invoking it; do noFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.