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/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/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/random6913/claude-code-superkit/dependency-checker"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/dependency-checker.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.00035 | $0.02322 |
| Opus 5.5 | $0.00014 | $0.00929 |
| Sonnet 5.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 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.
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.
- 1mo ago 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 (3 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 2,322 once invoked, about $0.0001 per session on Opus 5.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
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
deep-research-writer
Writes the single report.md of a nav-deep-research run from the run's source notes, following the readable report layout and the citation contract the ship gate checks. Spawned once by the nav-deep-research skill at step 3 (draft). Writes the report exactly once; later changes are the patcher's.
deep-research-critic
Adversarial reader of a nav-deep-research draft. Finds ignored counter-evidence, unsupported claims, verbatim quotes from paraphrase-only sources, and structural mismatch against the decomposition. Writes a findings JSON the patcher applies; cannot edit the report. Spawned once at step 4 by the nav-deep-research skill.
task-planner
Implementation planning and task breakdown specialist. Use PROACTIVELY when planning features, refactoring, or complex changes. Creates detailed implementation plans with effort estimates.
Lyra
Writer/builder instrument. Takes a complete spec, returns a diff or built artifact. Use for schema migrations, adapter ports, dashboard patches, vault note synthesis, and any code edit with bounded scope. Reports honesty ledger on completion.
Hestia
Vault custodian instrument. Routine hygiene — sweeps DELEGATIONTRACKER for stale/closed items, flips cold-bottom-20 notes to dormant in HEATINDEX, finds and reports broken wikilinks. Tends the hearth. Voice is terse, factual, lists what was swept. Cadence: 7-day. Edit-capable for status field updates.