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 skills/wojcikmm/spec-development-protocol/write-testsnpx skills add WojcikMM/spec-development-protocol --skill write-testsgit clone --depth 1 https://github.com/WojcikMM/spec-development-protocolWhat 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.00013 | $0.00313 |
| Opus 5 | $0.00006 | $0.00156 |
| Sonnet 5 | $0.00003 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
write-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 2d 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
Skill: Write Tests
Purpose
Produce maintainable tests that validate behavior, not implementation, to give the team confidence to ship and refactor.
Prerequisites
- Acceptance criteria are clear.
- Testing stack is specified in
TECH.md.
Checklist
- Test Cases: Enumerate test cases from acceptance criteria: happy path, error paths, and edge cases.
- Structure (AAA): Structure each test using Arrange-Act-Assert.
- Arrange: Set up inputs and mocks.
- Act: Invoke the code under test.
- Assert: Verify the outcome.
- Naming: Name tests descriptively, like
should <do something> when <condition>. - Focus: Focus on a single assertion per test where possible.
- Behavior, not Implementation: Test what the code does, not how it does it.
- Integration Tests: Test contracts at boundaries (HTTP, DB). Use real or in-memory implementations where practical. Cover auth paths. Reset state between tests.
- General: Don't skip failing tests—fix or delete them. Co-locate tests with source files.
Quality Bar
- Every acceptance criterion is tested.
- All scenarios (happy, error, edge) are covered.
- Tests are isolated and deterministic (no network calls or global state).
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.
- 2d ago First seen · 35 lines · 13 tokens per session scan A 1246bcc42b57
write-tests is a skill published in the GitHub repository WojcikMM/spec-development-protocol (2 stars, last pushed 22d ago), licensed MIT. It adds 13 tokens to every session and 313 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
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
write-tests
Write failing tests from requirements. Invoke for each todo before /implement.
dart-add-unit-test
Write and organize unit tests for functions, methods, and classes using package:test. Use when creating new logic or fixing bugs to ensure code remains correct and regression-free.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
myco:runtime-bootstrap-and-test-isolation
Activate this skill when adding a new manager, adding a new tool category, writing or debugging tool unit tests, diagnosing tool-visibility failures, investigating startup performance, or extending/maintaining/debugging the two-tier tool discovery system (toolindex) — even if the user doesn't explicitly ask about the…