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/lintgit 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.00009 | $0.00121 |
| Opus 5 | $0.00005 | $0.00060 |
| Sonnet 5 | $0.00002 | $0.00024 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
lint 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 2d 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.
What it actually says
Run linting checks:
- Type-checker (e.g.
pnpm typecheck,tsc --noEmit) - Linter (e.g.
pnpm lint,eslint .,ruff check .) - Formatter check (e.g.
prettier --check .,ruff format --check .)
Report any violations with file, line, and fix suggestion.
If a lint command doesn't exist or isn't configured, say so explicitly instead of silently skipping it.
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.
- 2d ago First seen · 16 lines · 9 tokens per session scan A 391e15877247
lint is a command published in the GitHub repository codeverbojan/claude-code-kickstart (2 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 121 once invoked, about $0.0000 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
plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
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.
taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
_subagent-discovery
Whenever a command needs to pick a subagent for a task (planning, task generation, or implementation execution). Do not hardcode agent names in command templates. Do not assume a specific agent exists.