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.
git clone --depth 1 https://github.com/ypollak2/claude-code-kickstartWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/ypollak2/claude-code-kickstart/dependency-auditor)<a href="https://agentmods.dev/agents/ypollak2/claude-code-kickstart/dependency-auditor"><img src="https://agentmods.dev/badge/agents/ypollak2/claude-code-kickstart/dependency-auditor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/ypollak2/claude-code-kickstart/dependency-auditor"><img src="https://agentmods.dev/badge/agents/ypollak2/claude-code-kickstart/dependency-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00020 | $0.00547 |
| Opus 5.5 | $0.00008 | $0.00219 |
| Sonnet 5.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 1mo 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.
- 1mo 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 6mo ago), licensed MIT. It adds 20 tokens to every session and 547 once invoked, about $0.0001 per session on Opus 5.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
test-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
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.
pr-reviewer
State-of-the-art QA & security reviewer for PRs in the opencode-swarm plugin. Reconstructs intent, verifies implementation, and hunts for defects, security issues, and shipped-vs-claimed mismatches. Operates read-only. Never approves without positive evidence. Never invents repository facts.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Metis Verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.
researcher
External documentation and API research.