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/codeverbojan/claude-code-kickstartWrote 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/codeverbojan/claude-code-kickstart/learn)<a href="https://agentmods.dev/commands/codeverbojan/claude-code-kickstart/learn"><img src="https://agentmods.dev/badge/commands/codeverbojan/claude-code-kickstart/learn/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/codeverbojan/claude-code-kickstart/learn"><img src="https://agentmods.dev/badge/commands/codeverbojan/claude-code-kickstart/learn.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.00013 | $0.00982 |
| Opus 5.5 | $0.00005 | $0.00393 |
| Sonnet 5.5 | $0.00003 | $0.00196 |
| Haiku 4.5 | $0.00001 | $0.00098 |
Grade A, and why
learn 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 2mo 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Learn Project Patterns
Analyze this codebase and generate (or update) patterns.md at the project root.
Do NOT ask questions — discover everything from the code. Do NOT write generic
advice — only document patterns that actually exist in this codebase.
What to Extract
For each category below, search the codebase for real examples. If a pattern doesn't exist in this project, skip that category entirely.
1. Error Handling
- How are errors created? (custom error classes, error factories, Result types)
- How are errors caught? (try/catch, middleware, error boundaries)
- Where is the error handler? (file path + pattern)
- Example: "All API routes use try/catch → AppError → errorHandler middleware"
2. Test Structure
- Where do tests live? (co-located,
__tests__/,tests/,test/) - What framework? (vitest, jest, pytest, go test)
- Fixtures/mocks: where and how?
- Is the DB mocked or real in tests?
- Example: "Tests mirror src/. Fixtures in fixtures/. Real test DB, no mocks."
3. Import / Module Patterns
- Path aliases? (check tsconfig.json paths, pyproject.toml, go.mod)
- Barrel exports? (index.ts files that re-export)
- Circular dependency patterns to avoid?
- Example: "@/ maps to src/. Each module has index.ts barrel export."
4. API / Route Patterns
- Route file structure (file-based routing, controller pattern, etc.)
- Middleware chain (auth → validate → handler → error)
- Request/response types (Zod schemas, Pydantic, typed structs)
- Example: "app/api/[resource]/route.ts. Auth middleware in middleware.ts."
5. Component Patterns (if frontend)
- Server vs client component split
- Styling approach (CSS Modules, Tailwind, styled-components)
- State management (context, zustand, redux)
- Naming conventions
- Example: "Server components by default. 'use client' only in interactive/"
6. Database Patterns
- ORM/query builder (Drizzle, Prisma, SQLAlchemy, sqlx)
- Migration approach
- Naming conventions (snake_case tables, camelCase fields?)
- Example: "Drizzle ORM. Migrations in packages/db/migrations/."
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.
- 2mo ago First seen · 116 lines · 13 tokens per session scan A 774e0c998583
learn is a command published in the GitHub repository codeverbojan/claude-code-kickstart (2 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 982 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-08-31.
Other commands, from other repositories
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.
_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.
amby.plan
Produce the technical implementation plan (the HOW) from an approved spec and UI.
amby.clarify
Resolve the open [NEEDS CLARIFICATION] markers in a feature spec.