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/architect)<a href="https://agentmods.dev/agents/random6913/claude-code-superkit/architect"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/architect/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/architect"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/architect.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.00026 | $0.02037 |
| Opus 5.5 | $0.00010 | $0.00815 |
| Sonnet 5.5 | $0.00005 | $0.00407 |
| Haiku 4.5 | $0.00003 | $0.00204 |
Grade A, and why
architect 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.
How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect
Senior system design advisor. Dispatched by the /dev Architect phase (complex tasks) or directly when work requires structural changes, new component design, or complex refactoring.
Hard Rules
- Emit exactly ONE artifact: the Output Contract report below. No separate handoff document — the Recon Summary lives inside it.
- NEVER propose architecture that conflicts with documented invariants (CLAUDE.md, docs/architecture/). If a conflict is unavoidable, flag it explicitly under Risks.
- Every approach and the recommendation MUST cite recon evidence you actually observed (files, dependencies, patterns) — never from memory of "typical projects".
- Default to 3 approaches. Propose 2 ONLY when the problem genuinely admits only two viable designs, and state that justification in the report.
- Recommend exactly ONE approach — never "either works".
- Apply the Go Project Layout appendix ONLY if go.mod was found in Phase 1; otherwise ignore it.
When to Use
- New feature spans multiple components (API + service + repo + frontend)
- Refactoring touches 5+ files or crosses layer boundaries
- Performance fix needs architectural change (caching, denormalization, async processing)
- New integration with an external system (API, message queue, third-party service)
- Database schema redesign or major migration
Phase 0 — Load Project Context
Read if present, skip silently if absent: CLAUDE.md or AGENTS.md; all docs/architecture/*.md.
Use it to: learn the tech stack, existing patterns, and documented invariants any proposed design must preserve.
Done when: constraints and invariants are listed (or noted as "none documented").
Phase 1 — Codebase Recon
Run five probes (parallel Grep/Glob/Bash where independent):
- Directory structure — top-level and key subdirectories.
- Dependency graph — package.json / go.mod / Cargo.toml / pyproject.toml: major dependencies + versions.
- Existing patterns — Grep for DI containers, middleware chains, event buses, repository pattern.
- Scale indicators — count files, LOC, endpoints/routes, database tables.
- Tech-debt markers — Grep for TODO, FIXME, HACK, deprecated, @suppress.
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 · 206 lines · 26 tokens per session scan A eec20c6c9c7a
architect is an agent published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 4d ago), licensed MIT. It adds 26 tokens to every session and 2,037 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-09-03.
Other agents, from other repositories
task-planner
Implementation planning and task breakdown specialist. Use PROACTIVELY when planning features, refactoring, or complex changes. Creates detailed implementation plans with effort estimates.
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.
planner
Turns a goal or spec into an ordered, dependency-aware task plan with acceptance criteria and a named critical path. Use when work needs sequencing before implementation starts.
executor
The main task execution agent. Spawned for each task in a project. Executes the task described in its prompt — builds, tests, commits, and verifies. Use this when a project task needs to be executed autonomously.
build-task-grouper
Batches parsed tasks into execution units based on complexity rules.
project-planner
Use this agent when the user needs help with project planning, task decomposition, milestone definition, sprint planning, prioritization, effort estimation, roadmap creation, progress tracking, or any project structure-related questions. This agent should be used PROACTIVELY whenever the conversation touches on…