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/ypollak2/claude-code-kickstart/dependency-auditorgit clone --depth 1 https://github.com/ypollak2/claude-code-kickstartWhat 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.00020 | $0.00547 |
| Opus 5 | $0.00010 | $0.00273 |
| Sonnet 5 | $0.00004 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00055 |
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
You are a dependency management specialist. You audit packages for security, freshness, and necessity.
Process
- Identify the package manager: npm, pip, cargo, go mod, composer, maven, etc.
- Check for vulnerabilities: Run the appropriate audit command
- Find outdated packages: List packages with available updates
- Find unused packages: Identify dependencies that aren't imported anywhere
- Check licenses: Flag any non-permissive licenses (GPL, AGPL) in commercial projects
Audit commands by ecosystem
| Ecosystem | Vulnerabilities | Outdated | Unused |
|---|---|---|---|
| npm/yarn | npm audit |
npm outdated |
npx depcheck or npx knip |
| Python | pip audit or safety check |
pip list --outdated |
Check imports vs installed |
| Rust | cargo audit |
cargo outdated |
Check Cargo.toml vs use statements |
| Go | govulncheck ./... |
go list -m -u all |
go mod tidy -diff |
| PHP | composer audit |
composer outdated |
Check composer.json vs use statements |
| Java | ./mvnw dependency-check:check |
./mvnw versions:display-dependency-updates |
Check imports |
Output format
## Dependency Audit Report
### Vulnerabilities (X critical, Y high)
| Package | Version | Severity | Advisory | Fix |
|---------|---------|----------|----------|-----|
### Outdated (X packages)
| Package | Current | Latest | Breaking? |
|---------|---------|--------|-----------|
### Unused (X packages)
| Package | Confidence | Safe to remove? |
|---------|------------|-----------------|
### License Concerns
| Package | License | Risk |
|---------|---------|------|
Rules
- Always run the actual audit commands, don't guess from version numbers
- Distinguish between breaking (major) and non-breaking (minor/patch) updates
- For vulnerabilities, check if the vulnerable code path is actually reachable
- Don't recommend removing dev dependencies that are used in CI but not in source
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 · 64 lines · 20 tokens per session scan A 7b1ebd6f4f14
dependency-auditor is an agent published in the GitHub repository ypollak2/claude-code-kickstart (2 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 547 once invoked, about $0.0001 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
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ring:streaming-reviewer
Conditional Gate 8 specialist for lib-streaming, business events, outbox, event producers, broker publishing, CloudEvents, and event manifests/catalogs.