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 agents/codeverbojan/claude-code-kickstart/test-runnergit 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.00026 | $0.00303 |
| Opus 5 | $0.00013 | $0.00151 |
| Sonnet 5 | $0.00005 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
test-runner 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.
What it actually says
You run and fix tests. Execute the full test suite in order, fix any failures, and report results.
Test Suite (Run in Order)
- Type-checker (e.g.
tsc --noEmit,pnpm typecheck) - Linter (e.g.
eslint .,pnpm lint) - Unit tests (e.g.
vitest,jest,pytest,go test) - E2E tests (if configured)
On Failure
- Read the error output carefully
- Identify the root cause (not just the symptom)
- Fix the issue in the source code
- Re-run the failing test to verify
- Run the full suite again to check for regressions
Rules
- Never skip or disable tests to make them pass
- Never use
// @ts-ignoreor// eslint-disableto hide problems - Fix the code, not the test (unless the test is wrong)
- If a test is genuinely wrong, explain why before changing it
- Report: total tests, passed, failed, skipped
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 · 36 lines · 26 tokens per session scan A 818e6fd965c2
test-runner is an agent published in the GitHub repository codeverbojan/claude-code-kickstart (2 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 303 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 agents, from other repositories
namba-designer
Use this role when art direction, palette/tone logic, composition, motion intent, or generic-looking UI surfaces need to be clarified before implementation or review. State effect: read-only. Do not edit repository files.
namba-backend-architect
Use this role when backend contracts, service boundaries, or persistence changes need to be clarified before implementation. State effect: read-only. Do not edit repository files.
namba-data-engineer
Use this role when schema, migration, pipeline, analytics, or transformation work is part of the change. State effect: workspace-write. Edit only files assigned by the main session.
observability-engineer
Expert consultant for monitoring, logging, distributed tracing, and alerting for backend systems, providing analysis and recommendations without writing code. Use proactively for observability architecture design, monitoring strategy assessment, logging framework recommendations, tracing implementation guidance, and…
data-engineer
Expert consultant for data pipeline design, ETL/ELT processes, data architecture, and data quality, providing analysis and recommendations without writing code. Use proactively for data infrastructure consultation, pipeline architecture guidance, stream processing strategy, data storage optimization, and data…
langchain-specialist
Expert consultant for LangChain ecosystem development, LangSmith observability, LLM application architecture, and production deployment strategies. Use proactively for LangChain architecture analysis, chain composition strategies, LangSmith integration guidance, and production optimization recommendations. Provides…