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/codeverbojan/claude-code-kickstart/initgit clone --depth 1 https://github.com/codeverbojan/claude-code-kickstartWhat 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.00019 | $0.00747 |
| Opus 5 | $0.00010 | $0.00374 |
| Sonnet 5 | $0.00004 | $0.00149 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
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 yesterday.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-Configure Project
Analyze this codebase and generate a complete Section 10 for CLAUDE.md. Do NOT ask the user questions — discover everything from the code.
1. Detect Stack
Check for these files and determine the stack:
package.json→ Node.js / TypeScriptgo.mod→ GoCargo.toml→ Rustpyproject.toml/requirements.txt/setup.py→ PythonGemfile→ Rubypom.xml/build.gradle→ Java/Kotlincomposer.json→ PHP*.csproj/*.sln→ C# / .NETmix.exs→ Elixirpubspec.yaml→ Flutter/Dart- Multiple → list all
2. Detect Commands
Node.js: Read package.json scripts field. Map to actual commands.
Python: Check Makefile, pyproject.toml [tool.pytest], tox.ini.
Go: Check Makefile targets. Default to go test/vet/build.
Rust: Default to cargo check/clippy/test/build.
Any stack: Check Makefile, justfile, Taskfile.yml, docker-compose.yml.
3. Detect Conventions
Read actual code to discover patterns (don't assume):
- TypeScript: Check
tsconfig.jsonfor strict mode. Check foranyusage. - Linting: Check
.eslintrc*,ruff.toml,.golangci.yml,clippy.toml. - Formatting: Check
.prettierrc*,biome.json,ruff.toml,rustfmt.toml. - Testing: Check test directory structure, framework config.
- CSS: Check for CSS modules, Tailwind, styled-components, etc.
- Components: Server vs client components, naming patterns.
- Imports: Barrel files, path aliases (
tsconfig.jsonpaths).
4. Detect Architecture
- Read the top-level directory structure
- Identify: monorepo (turbo.json, nx.json, lerna.json, pnpm-workspace.yaml)?
- Identify: app framework (Next.js app router, Django, Rails, FastAPI)?
- Map key directories to their purpose
- Note entry points (main files, route directories)
5. Write Section 10
Replace Section 10 in CLAUDE.md with what you discovered. Use this format:
## 10. Project-Specific Configuration
### Stack
[What you found]
### Build & Dev Commands
- `command` — what it does
- `command` — what it does
### Code Conventions
- [Convention discovered from config files]
- [Convention discovered from code patterns]
### Architecture
[Directory structure with purpose of each key directory]
[Entry points]
[Key patterns: monorepo, app router, etc.]
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.
- yesterday First seen · 87 lines · 19 tokens per session scan A 336958650e6a
init is a command published in the GitHub repository codeverbojan/claude-code-kickstart (2 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 747 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-08-31.
Other commands, from other repositories
stats
Show token-saver compression statistics and savings.
implement
Execute implementation by processing atomic task files one at a time with Context Pinning (Atomic Traceability Model).
cleanup
Detect and remove orphaned code, unused components, dead routes, and stale database artifacts.
specify
Create or update the feature specification from a natural language feature description.
_registry-protocol
This protocol is MANDATORY for ALL commands, agents, and phases.
amby.converge
Check the codebase against spec, plan, and tasks after implementing; append gap tasks, never edit code.