superkit-init

superkit-init is a command for Claude Code from RaNDoM6913/claude-code-superkit. It costs 18 tokens per session (3,049 once invoked), scanned A, original, MIT.

A command that reads an existing codebase and creates project documentation from what the code actually contains. It can also configure project rules and hooks using paths found in the project.

In plain words
What is it for?
Use it when starting documentation for an existing project, or when setting up an empty project interactively or automatically.
Why use it?
It removes the need to fill in empty documentation templates or guess the project's languages, structure, and architecture. Unknown details are marked for later clarification.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

Good fit Use it when starting documentation for an existing project, or when setting up an empty project interactively or automatically.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/random6913/claude-code-superkit/superkit-init
Install

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.

Clone the repo
git clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkit

Made for: Claude Code.

Wrote 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.

agentmods badge for superkit-init

README.md
[![agentmods](https://agentmods.dev/badge/commands/random6913/claude-code-superkit/superkit-init/github.svg)](https://agentmods.dev/commands/random6913/claude-code-superkit/superkit-init)
Your own site
<a href="https://agentmods.dev/commands/random6913/claude-code-superkit/superkit-init"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/superkit-init/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.

agentmods 80×15 button for superkit-init

Your own site · 80×15
<a href="https://agentmods.dev/commands/random6913/claude-code-superkit/superkit-init"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/superkit-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,049 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.03049
Opus 5.5 $0.00007 $0.01220
Sonnet 5.5 $0.00004 $0.00610
Haiku 4.5 $0.00002 $0.00305

Measured 1mo ago against content hash 54bdeae883fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

superkit-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 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.

packages/core/commands/superkit-init.md · 275 lines

How it starts

The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Superkit Init — Intelligent Project Setup

Role

Scan the codebase, generate filled documentation (not empty templates), and configure superkit rules/hooks with real project paths. Replaces manual CLAUDE.md filling, architecture doc writing, and rule configuration.

Parse $ARGUMENTS:

  • Empty (default) → interactive: pause at every checkpoint.
  • --non-interactive → skip all checkpoints and questions, generate everything automatically.

Hard Rules

  1. Detect by reading code. Do NOT ask the user what their stack is — the only permitted question is the Scaffold stack question (interactive mode, empty project).
  2. Generated docs describe what EXISTS in the code, not what should exist.
  3. ALL generated text is English, including TODO placeholders.
  4. Architecture doc filenames come ONLY from the canonical table in Step 2 — never invent name variants.
  5. When something cannot be determined from code, write TODO: [specific question] — never guess.
  6. Every generated file starts with the generation stamp (Step 2).
  7. Emit the final report ONLY after the Done-when gate in Step 5 passes.

Scaffold path (empty project)

Step 1 declares Scaffold when NO language marker exists (no go.mod, package.json, Cargo.toml, pyproject.toml, requirements.txt). All steps still run in order; this matrix defines each step's behavior:

Step Full project Empty project (Scaffold)
1 Scan Full detection Record "empty project". Interactive: ask "What stack will you use? [Go / TypeScript / Python / Rust / Other]". Non-interactive: stack = TODO: define the stack
2 Generate Arch docs + trees + CLAUDE.md Minimal CLAUDE.md only (project name, stack answer or the TODO above, empty structure). No arch docs, no trees
3 Configure rules Real-path mapping SKIP — no real paths exist yet; record "rules not configured (empty project)" for the report
4 Validate All 3 checks Single check: CLAUDE.md exists and starts with the generation stamp
5 Commit & report Full report git add CLAUDE.md only; use the Scaffold report variant

Read the full file on GitHub · 275 lines

Changes

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.

  1. 1mo ago First seen · 275 lines · 18 tokens per session scan A 54bdeae883fa

Subscribe to this mod's changes

superkit-init is a command published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 3,049 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.