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/test)<a href="https://agentmods.dev/commands/codeverbojan/claude-code-kickstart/test"><img src="https://agentmods.dev/badge/commands/codeverbojan/claude-code-kickstart/test/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/test"><img src="https://agentmods.dev/badge/commands/codeverbojan/claude-code-kickstart/test.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.00008 | $0.00142 |
| Opus 5.5 | $0.00003 | $0.00057 |
| Sonnet 5.5 | $0.00002 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
test 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.
What it actually says
Run the test suite in this order:
- Type-checker (e.g.
pnpm typecheck,tsc --noEmit,mypy .) - Linter (e.g.
pnpm lint,eslint .,ruff check .) - Unit tests (e.g.
pnpm test,vitest,jest,pytest,go test ./...) - E2E tests (if configured)
Report results clearly. Fix any failures before reporting success.
If a test 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.
- 1mo ago First seen · 17 lines · 8 tokens per session scan A a94b922f449d
test is a command published in the GitHub repository codeverbojan/claude-code-kickstart (2 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 142 once invoked, about $0.0000 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
test-suite
Run comprehensive test suite with coverage analysis.
flutter-test
Run Flutter/Dart tests, report failures, and incrementally fix test issues. Covers unit, widget, golden, and integration tests.
qa-automation
Set up a comprehensive test automation strategy.
svelte:test-fix
Troubleshoot and fix failing tests in Svelte/SvelteKit projects, including debugging test issues and resolving common testing problems.
svelte:test-setup
Set up comprehensive testing infrastructure for Svelte/SvelteKit projects, including unit testing, component testing, and E2E testing frameworks.
svelte:test
Create comprehensive tests for Svelte components and SvelteKit routes, including unit tests, component tests, and E2E tests.