Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/brain-bootstrap/claude-code-brain-bootstrap/depsnpx skills add brain-bootstrap/claude-code-brain-bootstrap --skill depsgit clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrapWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00045 | $0.00442 |
| Opus 5 | $0.00023 | $0.00221 |
| Sonnet 5 | $0.00009 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
deps scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Deps Skill
Manage project dependencies following the CVE decision tree.
Usage
/deps check # Show outdated packages
/deps update lodash # Update specific package
/deps audit # Run security audit
/deps why express # Explain why a package is installed
/deps dedupe # Deduplicate dependency tree
Instructions
First: Read claude/cve-policy.md for the CVE decision tree.
Determine action from $ARGUMENTS:
| Argument | Action |
|---|---|
check |
Show outdated packages |
update <package> |
Update specific package |
audit |
npm audit / pip audit / cargo audit / bundle audit |
why <package> |
npm why <package> / pip show <package> |
dedupe |
npm dedupe / pnpm dedupe |
| (empty) | Run check + audit |
By Package Manager:
npm / pnpm / yarn:
pnpm outdated 2>&1 | head -40
pnpm audit --audit-level moderate 2>&1 | head -40
pip / uv / poetry:
pip list --outdated 2>&1 | head -30
pip-audit 2>&1 | head -40
cargo:
cargo outdated 2>&1 | head -30
cargo audit 2>&1 | head -40
CVE Response Rules (from claude/cve-policy.md):
- Critical/High severity → upgrade immediately, test, PR same day
- Medium severity → schedule within current sprint
- Low severity → batch with next dependency update cycle
- NEVER blindly upgrade majors — check breaking changes first
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 60 lines · 45 tokens per session scan A ee1c31abe499
deps is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 442 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
implement
TRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/wip plan OR a standalone task (bug fix, GitHub issue, one-off change). Examples: "work on task 1", "fix this bug", "implement feature X from the issue". Provides structured execution with profile detection, dependency…
review-spec
Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.
chain-of-verification
Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.
review-code
Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.
review-design
Review design, implementation, and task documents produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.
design
Use in pre-implementation (idea-to-design) stages to understand spec/requirements and create a correct implementation plan before writing actual code. Turns ideas into a fully-formed PRD/design/specification and implementation-plan. Creates design docs and task lists in docs/wip/.