agentmods.dev

spekka: Skill for Claude Code

.claude/skills/spekka-testing-test-writing/SKILL.md

Testing Test Writing is a skill for Claude Code from johnreitano/spekka. It costs 27 tokens per session (271 once invoked), scanned A, original, MIT.

A set of guidelines for writing tests, which are programs that check whether software behaves as expected. It favors a small number of fast tests for important user journeys and tests the behavior users depend on.

In plain words
What is it for?
Use it after completing a feature to test core user flows. It helps choose what to test, write clear test names, isolate external dependencies, and avoid brittle implementation-specific tests.
Why use it?
It avoids spending development time testing every minor change or low-priority edge case. Mocking outside systems such as databases and APIs keeps tests isolated and quick.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code.

This is johnreitano/spekka's own configuration. It tells Claude Code how to work on spekka itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything spekka configures →

not rated 5repo 9mo ago A scan 27 tokens original MIT
View source ↗ johnreitano/spekka
Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/johnreitano/spekka/main/.claude/skills/spekka-testing-test-writing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/johnreitano/spekka

Made for: Claude Code.

Wrote 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.

agentmods badge for Testing Test Writing

README.md
[![agentmods](https://agentmods.dev/badge/skills/johnreitano/spekka/spekka-testing-test-writing/github.svg)](https://agentmods.dev/skills/johnreitano/spekka/spekka-testing-test-writing)
Your own site
<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.

agentmods 80×15 button for Testing Test Writing

Your own site · 80×15
<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>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 271 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.00271
Opus 5.5 $0.00011 $0.00108
Sonnet 5.5 $0.00005 $0.00054
Haiku 4.5 $0.00003 $0.00027

Measured 2mo ago against content hash 7ffe3328eaba, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/skills/spekka-testing-test-writing/SKILL.md · 19 lines

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
Changes

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.

  1. 2mo ago First seen · 19 lines · 27 tokens per session scan A 7ffe3328eaba

Subscribe to this mod's changes

Testing Test Writing is a skill published in the GitHub repository johnreitano/spekka (5 stars, last pushed 9mo ago), licensed MIT. It adds 27 tokens to every session and 271 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.

Testing
Related

Testing Test Writing compared with skills from other repositories

Testing Test Writing next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
Testing Test Writingjohnreitano/spekkaSkill59mo agoMITA27Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code