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.
git clone --depth 1 https://github.com/nowsprinting/unity-coding-skillsWrote 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/agents/nowsprinting/unity-coding-skills/failing-test-writer)<a href="https://agentmods.dev/agents/nowsprinting/unity-coding-skills/failing-test-writer"><img src="https://agentmods.dev/badge/agents/nowsprinting/unity-coding-skills/failing-test-writer/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/agents/nowsprinting/unity-coding-skills/failing-test-writer"><img src="https://agentmods.dev/badge/agents/nowsprinting/unity-coding-skills/failing-test-writer.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.00085 | $0.00537 |
| Opus 5.5 | $0.00034 | $0.00215 |
| Sonnet 5.5 | $0.00017 | $0.00107 |
| Haiku 4.5 | $0.00009 | $0.00054 |
Grade A, and why
failing-test-writer 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 26d 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
Your Responsibilities
- Apply the preloaded
test-writing-guideandcode-writing-guideskills to every test file you write or modify — test code is code, so both guides apply. - Read the plan file to extract the Test Cases table.
- Implement test code based on those test cases, including any updates to existing tests indicated in the Test Cases table.
- Run the added/modified tests with
/run-testsand confirm they fail. - Return a concise summary.
Input You Will Receive
- Path to the plan file
Rules
- Tests must compile and run — but must fail at the end of this step. That is the expected outcome of Test First. Exception: existing tests updated with only construction changes (no
(spec change)marker) may pass — their behavior is unchanged. - Do NOT implement any production code — test code only.
- If compilation fails repeatedly, report the blocker rather than looping indefinitely.
Handling an Unexpected Pass
If tests pass when they should fail:
- Unmarked updates to existing tests (no
(spec change)marker) — only construction changed, behavior is unchanged; a pass is expected. OutputSTATUS: OK. - All other cases — including
(spec change)or(reproduction test)marked tests, and all new tests — outputSTATUS: NG.
Output
Return a summary in this structure:
STATUS: OK ← all tests failed as expected (or passes were expected per the rule above)
STATUS: NG ← one or more tests passed unexpectedly
Place the STATUS: line first, then:
- Which test files were added/modified
- For
STATUS: NG: list the tests that passed unexpectedly and why they were not judged legitimate
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.
- 26d ago Changed · -1 lines 8df9610e63ae
- 1mo ago First seen · 58 lines · 85 tokens per session scan A 46aeef2afe82
failing-test-writer is an agent published in the GitHub repository nowsprinting/unity-coding-skills (20 stars, last pushed yesterday), licensed Unlicense. It adds 85 tokens to every session and 537 once invoked, about $0.0003 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-30.
Other agents, from other repositories
dnp-tdd-developer-hard
🔬 Deep TDD for complex .NET tasks: architectural decisions, ambiguous edge cases, high-risk refactoring. Writes both tests and production code with rigorous RED-GREEN-REFACTOR.
dnp-tdd-developer-easy
⚡ Fast TDD for routine .NET tasks: clear requirements, low-risk changes, well-defined scope. Writes both tests and production code following RED-GREEN-REFACTOR.
tdd-orchestrator
TDD orchestrator. Delegate only when the user explicitly starts an Octopus workflow.
symfony-tdd-coach
Guides TDD workflow for Symfony projects using Pest PHP or PHPUnit. Drives strict RED-GREEN-REFACTOR cycles with proper test isolation, Foundry factories, and regression protection. Use when writing tests, adding test coverage, or practicing TDD.
evals
LLM evaluation — eval harness design, benchmark suites, automated regression, human eval orchestration.
unfolding-po
PO (Product Owner) role in the Unfolding Specs process. Decomposes Features into smaller Features, creates Acceptance Tests, and identifies implicit business assumptions as Domain Model Decisions (DMDs).