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 commands/random6913/claude-code-superkit/docs-initgit 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/docs-init)<a href="https://agentmods.dev/commands/random6913/claude-code-superkit/docs-init"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/docs-init.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.00013 | $0.00762 |
| Opus 5 | $0.00006 | $0.00381 |
| Sonnet 5 | $0.00003 | $0.00152 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
docs-init 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 today.
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Project Documentation
Role
Set up project documentation. Prefer /superkit-init (intelligent scan + auto-populated docs). Run the manual fallback ONLY when that command is not installed.
Hard Rules
- If
/superkit-initexists, redirect to it and stop — never also run the fallback. - Never overwrite an existing root
CLAUDE.md; create it only when absent. - Never reference kit-source paths (
packages/...); they do not exist in installed projects. Use the inline skeleton below. - Fallback touches only:
docs/architecture/,docs/trees/, andCLAUDE.md(when absent). - Forward the caller's arguments to
/superkit-initunchanged.
Steps
-
Detect the preferred command. Glob
.claude/commands/superkit-init.md.- Found → do Step 2 (redirect).
- Not found → do Step 3 (fallback).
- Done-when: you have chosen redirect or fallback.
-
Redirect (preferred). Invoke
/superkit-init, forwarding the caller's arguments verbatim: $ARGUMENTS Then stop — do NOT run Step 3.- Done-when:
/superkit-initfinished and its report is shown.
- Done-when:
-
Fallback scaffold (only when Step 1 found no
superkit-init.md):mkdir -p docs/architecture docs/trees- Dispatch the
tree-generatoragent to populatedocs/trees/. If the agent is unavailable, note it and skip. - Read the project root: if
CLAUDE.mdalready exists, leave it unchanged. If absent, Write it from the skeleton below, keeping theTODO:markers for the user to fill in.
- Done-when: both dirs exist, trees generated (or skipped with a note), and a root
CLAUDE.mdexists.
Inline CLAUDE.md skeleton (used by fallback Step 3, only when no root CLAUDE.md exists)
# YOUR_PROJECT_NAME
> TODO: one-line project description.
## Tech Stack
TODO: backend / frontend / infra.
## Structure
TODO: top-level directory layout.
## Key Commands
TODO: build / test / lint / migrate / dev-server commands.
## Conventions
TODO: formatting, error handling, commit format, API style, env vars.
## Architecture Reference
| Doc | Description |
|-----|-------------|
| docs/architecture/*.md | TODO: fill in per generated template |
| docs/trees/tree-monorepo.md | Project directory structure |
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.
- today First seen · 76 lines · 13 tokens per session scan A 708df2f31f69
docs-init is a command published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 762 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
triage-issue
Apply labels + milestone + priority to a new issue using the llmwiki triage rules.
team
Build a team of Conductor workspaces (with roles) and dispatch tasks to it.
init
Initialize dev-flow project — scan current state, create/align .dev-doc, update agent instruction file.
issue-implement
Implement a specific stage of an issue's implementation plan using feature-dev.
setup-mcp-claude-code
Build and register the Contorium MCP server for Claude Code or Cursor Agent.