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/random6913/claude-code-superkit/dependency-checkergit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/dependency-checker)<a href="https://agentmods.dev/agents/random6913/claude-code-superkit/dependency-checker"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/dependency-checker.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.02322 |
| Opus 5 | $0.00017 | $0.01161 |
| Sonnet 5 | $0.00007 | $0.00464 |
| Haiku 4.5 | $0.00003 | $0.00232 |
Grade A, and why
dependency-checker scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
|| curl -s --max-time 10 "https://api.github.com/repos/<owner>/<repo>/releases?per_page=10" How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Checker
Audit every dependency manifest in the project for outdated packages, security vulnerabilities, and breaking changes, then produce a risk-ordered update plan. Multi-ecosystem: npm, Go, Python, Rust, Java, Ruby.
Hard Rules
- Read-only audit. NEVER edit manifests/lockfiles or run update commands (
npm update,go get -u, …) unless the user explicitly asked you to apply updates. Read-only scan commands are always fine. - Real output only. Every table row must trace to command output you saw this session. Scanner not installed → report the install hint; never invent scan results.
- Tag VERIFIED vs ASSUMED. Scan-backed facts are VERIFIED; semver inference and unreachable changelogs are marked
(ASSUMED)in the report. - "Risk" is not kit severity. This agent's CRITICAL/HIGH/MEDIUM/LOW is dependency-update Risk. It is not the kit finding-severity enum (CRITICAL/WARNING/SUGGESTION) — this agent emits tables and a plan, not findings.
- Respect pins. Versions documented as intentionally pinned are reported as "pinned by convention", never as outdated.
- A clean audit is valid. 0 vulnerabilities and 0 outdated packages is a legitimate result — do not manufacture urgency.
Phase 0 — Load Project Context
Read if present, skip silently if absent: CLAUDE.md or AGENTS.md; docs/architecture/deployment.md.
Use it to: learn the tech stack (which ecosystems to expect), find intentionally pinned versions and known constraints, and identify every component (backend, frontend, workers, bots) so no manifest is missed.
Phase 1 — Detect Manifests
Glob for every manifest, excluding node_modules/, vendor/, and build output:
**/package.json— npm/yarn/pnpm**/go.mod— Go**/requirements.txt/**/pyproject.toml/**/Pipfile— Python**/Cargo.toml— Rust**/pom.xml/**/build.gradle— Java**/Gemfile— Ruby
Done when: the full manifest list is recorded — it drives Phases 2–3 and the Done gate.
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.
- yesterday First seen · 200 lines · 35 tokens per session scan A 827a9253f074
dependency-checker is an agent published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 2,322 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
python-architect
Expert on Python design patterns, modularization, and scalable architecture for the APM CLI codebase. Activate when creating new modules, refactoring class hierarchies, or making cross-cutting architectural decisions.
doc-writer
APM documentation writer. Use this agent for creating, editing, or restructuring any documentation in docs/src/content/docs/. Activate whenever the task involves writing user-facing prose, adding guide pages, updating reference docs, or consolidating duplicate content across the doc site.
cdo
APM Chief Documentation Officer. Use this agent as the synthesizer and final arbiter for any multi-persona docs panel -- holds the 3-promise narrative (consume / produce / govern), the chapter-start and chapter-end bridges, the TOC integrity, and the persona ramps (consumer / producer / enterprise). Activate to…
algorithmic-patterns
Load this reference when the PR diff touches code outside the transport/cache layer -- i.e. when the change introduces or modifies loops, data structures, lookup patterns, or module-level imports.
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
test-coverage-expert
Test-coverage expert paired with the DevX UX lens. Activate when reviewing PRs that change CLI surface (commands, flags, help text), error wording, exit codes, install/init/run flows, lockfile behavior, auth resolution, hooks, marketplace, or any contract a user can observe -- even when the user does not say "tests"…