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/commands/random6913/claude-code-superkit/dev)<a href="https://agentmods.dev/commands/random6913/claude-code-superkit/dev"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/dev/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/commands/random6913/claude-code-superkit/dev"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/dev.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.00000 | $0.03766 |
| Opus 5.5 | $0.00000 | $0.01506 |
| Sonnet 5.5 | $0.00000 | $0.00753 |
| Haiku 4.5 | $0.00000 | $0.00377 |
Grade A, and why
dev 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.
| 1 | [specific, testable outcome] | [grep / curl / test / read] | Score ≥ 7 | MUST | How it starts
The opening of the file, as written. The whole thing — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Orchestrator
Run the full development cycle for the task below as 16 numbered phases. You are the orchestrator: you execute phases yourself and dispatch specialist agents at the gates.
Task
$ARGUMENTS
Hard Rules
- Execute phases in order 0 → 15. Skip a phase ONLY when the Skip Matrix says so for the task's complexity class.
- A phase is complete only when its Done when condition holds. If a phase produces errors, fix them before advancing.
- Consume gate verdicts exactly as produced: plan-checker → PASS/REVISE/BLOCK · evaluator → PROCEED/ITERATE/ESCALATE · goal-verifier → PASS/NEEDS-ATTENTION/NEEDS-REMEDIATION · critic → APPROVE/CONCERN/BLOCK.
- On any failed gate or retry, escalate effort to
maxfor the next attempt and say you are doing so — never silently re-run at the same effort. - Never claim completion while compilation or tests fail. The Phase 15 report is emitted only after every non-skipped phase has run.
- If the task is ambiguous, ask the user before Phase 7 (Implement) — not after.
- Always read existing patterns before writing new code — search first, reuse the closest implementation as reference.
Phase Overview & Skip Matrix
Complexity (Simple / Standard / Complex) is decided in Phase 1 and never changes mid-run.
| # | Phase | Simple | Standard | Complex | Gate agent |
|---|---|---|---|---|---|
| 0 | Read Docs | ✓ | ✓ | ✓ | — |
| 1 | Understand | ✓ | ✓ | ✓ | — |
| 2 | Architect | — | — | ✓ | architect |
| 3 | Pseudocode | — | — | ✓ | — |
| 4 | Plan | ✓ | ✓ | ✓ | — |
| 5 | Contract | — | ✓ | ✓ | — |
| 6 | Validate Plan | — | ✓ | ✓ | plan-checker |
| 7 | Implement | ✓ | ✓ | ✓ | — |
| 8 | Evaluate | — | ✓ (max 2 passes) | ✓ (max 3 passes) | evaluator |
| 9 | Verify | ✓ | ✓ | ✓ | health-checker |
| 10 | Test | ✓ | ✓ | ✓ | test-generator |
| 11 | Verify Goals | — | ✓ | ✓ | goal-verifier |
| 12 | Review | ✓ | ✓ | ✓ | reviewers (parallel) |
| 13 | Critic | — | — | ✓ | critic |
| 14 | Document | ✓ | ✓ | ✓ | docs-reviewer |
| 15 | Report | ✓ | ✓ | ✓ | — |
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 · 303 lines · 0 tokens per session scan A c4a4fd3c9e81
dev is a command published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,766 tokens. 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 commands, from other repositories
ccc-audit
Audit the current project for dependency vulnerabilities, oversized bundles, type errors, dead code, hardcoded secrets, undocumented env vars and a missing CLAUDE.md. Use when you want a health score before a release or review.
validate
Mechanically validate the sonu plugin repo before a PR — manifest sync, YAML frontmatter, shell-fence syntax, named-source and AI-attribution scans, cross-reference integrity, skill reachability. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
tester
Comprehensive testing with parallel execution capabilities.
boundary-heatmap
Generate a visual heatmap of knowledge boundaries showing safe zones, risk areas, and semantic coverage.
verify-work
Validate built features through conversational UAT.
checklist
Generate a custom checklist for the current feature based on user requirements.