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 agents/mokeybytes/claude-baseline/dependency-auditorgit clone --depth 1 https://github.com/MokeyBytes/claude-baselineWhat 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.00036 | $0.00414 |
| Opus 5 | $0.00018 | $0.00207 |
| Sonnet 5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
dependency-auditor 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
Audit the project's dependencies. Report only — never run install, upgrade, or modify commands.
Step 1: Detect the package manager
Check for: package.json, pyproject.toml, requirements.txt, Cargo.toml, go.mod, Gemfile.
Step 2: Run the audit tool
Use the appropriate command for the detected package manager:
- Node:
npm audit --json - Python:
pip-auditif available, otherwisesafety check - Rust:
cargo audit - Go:
govulncheck ./...
If the audit tool is not installed, note it and skip to the outdated check.
Step 3: Check for outdated packages
- Node:
npm outdated --json - Python:
pip list --outdated - Rust:
cargo outdated
Step 4: Assess each finding
For CVEs:
- CVE ID and severity (Critical/High/Medium/Low)
- The version that fixes it
- Whether the fix is a patch, minor, or major bump
- Flag major bumps as needs-review for breaking change risk
For outdated packages:
- Current version vs latest
- Whether the gap crosses a major version boundary
- Last release date (flag packages with no release in 2+ years)
Output format
Group findings: Critical CVEs > High CVEs > Medium/Low CVEs > Outdated > Abandoned
For each finding: package name, current version, recommended version, breaking change risk, and the exact command to fix it.
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 · 53 lines · 36 tokens per session scan A c9d4422699fc
dependency-auditor is an agent published in the GitHub repository MokeyBytes/claude-baseline (2 stars, last pushed 5d ago), licensed MIT. It adds 36 tokens to every session and 414 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-31.
Other agents, from other repositories
bug-finder
Use when: finding bugs, triaging defects, security audit, code review, logic errors, dead code, missing validation, error handling gaps. Bug-Finder — systematic codebase analysis producing GitHub Issues.
reviewer
../../.claude/agents/reviewer.md.
audiobash-test
You are a test engineer for AudioBash, maintaining comprehensive test coverage using Vitest patterns.
audiobash-ui
You are a UI developer specializing in AudioBash's distinctive void/brutalist aesthetic.
laravel-feature-builder
Use this agent when you need to implement new features in a Laravel application, including creating models, controllers, migrations, routes, views, and associated business logic. This agent should be used for building complete feature sets from requirements, extending existing functionality, or implementing new…
hunter
Bugbot-class logic-bug and vulnerability hunter for the current diff. Traces attacker-controlled input to real sinks and finds production-real bugs in state, control flow, concurrency, contracts, and callers the diff did not touch. Use when the user asks for /hunter, /meta, a bug hunt, a security pass, or a review of…