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 skills add codeverbojan/claude-code-kickstart --skill running-testsgit 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/skills/codeverbojan/claude-code-kickstart/running-tests)<a href="https://agentmods.dev/skills/codeverbojan/claude-code-kickstart/running-tests"><img src="https://agentmods.dev/badge/skills/codeverbojan/claude-code-kickstart/running-tests/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/skills/codeverbojan/claude-code-kickstart/running-tests"><img src="https://agentmods.dev/badge/skills/codeverbojan/claude-code-kickstart/running-tests.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.00029 | $0.00207 |
| Opus 5.5 | $0.00012 | $0.00083 |
| Sonnet 5.5 | $0.00006 | $0.00041 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
running-tests 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
Test Execution
Run Order
Always run in this order — faster checks first catch errors cheaply:
1. Type-checker (seconds — catches 80% of issues)
2. Linter (seconds — catches style + security)
3. Unit tests (seconds-minutes — catches logic)
4. Integration (minutes — catches wiring)
5. E2E (minutes — catches workflows, run last)
Failure Rules
- Type error → fix the type. Never
anyor@ts-ignore. - Lint error → fix the code. Disable only with written reason.
- Test failure → fix the code, not the test (unless the test is wrong).
- Show passing output in the same message. "I ran them earlier" is not evidence.
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 · 29 lines · 29 tokens per session scan A 36251fc1c01d
running-tests is a skill published in the GitHub repository codeverbojan/claude-code-kickstart (2 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 207 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 skills, from other repositories
gsd-add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
memstack-development-test-writer
Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.
ios-testing-patterns
XCTest and XCUITest execution workflows and flaky test detection patterns.
06-test
Write and iterate developer-side tests until they pass, or validate a user journey end to end in the browser during implementation. Use when the user wants to add coverage, find what's untested, or walk a flow while building it. Do NOT use for independent acceptance QA or reviewer evidence, auditing test health, or…
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
pdlc-quality
A quality gate that runs configured coverage, end-to-end, and lint checks, compares their real results with declared targets, and creates a report for human approval.