Borrowing it
Nothing to install: this file belongs to johnreitano/spekka. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/johnreitano/spekka/main/.claude/skills/spekka-testing-test-writing/SKILL.mdgit clone --depth 1 https://github.com/johnreitano/spekkaWrote 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/johnreitano/spekka/spekka-testing-test-writing)<a href="https://agentmods.dev/skills/johnreitano/spekka/spekka-testing-test-writing"><img src="https://agentmods.dev/badge/skills/johnreitano/spekka/spekka-testing-test-writing/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/johnreitano/spekka/spekka-testing-test-writing"><img src="https://agentmods.dev/badge/skills/johnreitano/spekka/spekka-testing-test-writing.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.00027 | $0.00271 |
| Opus 5 | $0.00014 | $0.00135 |
| Sonnet 5 | $0.00005 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
Testing Test Writing 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 10d 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
Testing Test Writing
This Skill provides Claude Code with specific guidance on how it should handle testing test writing.
Instructions
- Write Minimal Tests During Development: Do NOT write tests for every change or intermediate step. Focus on completing the feature implementation first, then add strategic tests only at logical completion points
- Test Only Core User Flows: Write tests exclusively for critical paths and primary user workflows. Skip writing tests for non-critical utilities and secondary workflows until if/when you're instructed to do so.
- Defer Edge Case Testing: Do NOT test edge cases, error states, or validation logic unless they are business-critical. These can be addressed in dedicated testing phases, not during feature development.
- Test Behavior, Not Implementation: Focus tests on what the code does, not how it does it, to reduce brittleness
- Clear Test Names: Use descriptive names that explain what's being tested and the expected outcome
- Mock External Dependencies: Isolate units by mocking databases, APIs, file systems, and other external services
- Fast Execution: Keep unit tests fast (milliseconds) so developers run them frequently during development
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.
- 10d ago First seen · 19 lines · 27 tokens per session scan A 7ffe3328eaba
Testing Test Writing is a skill published in the GitHub repository johnreitano/spekka (5 stars, last pushed 8mo ago), licensed MIT. It adds 27 tokens to every session and 271 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 skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.