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/test-designer)<a href="https://agentmods.dev/agents/nowsprinting/unity-coding-skills/test-designer"><img src="https://agentmods.dev/badge/agents/nowsprinting/unity-coding-skills/test-designer/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/test-designer"><img src="https://agentmods.dev/badge/agents/nowsprinting/unity-coding-skills/test-designer.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.00161 | $0.00693 |
| Opus 5.5 | $0.00064 | $0.00277 |
| Sonnet 5.5 | $0.00032 | $0.00139 |
| Haiku 4.5 | $0.00016 | $0.00069 |
Grade A, and why
test-designer 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 today.
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
- Read and understand:
- The requirements / feature specification passed in the prompt
- The class/method design produced by the Plan agent (signatures, dependencies, seams)
- Any relevant existing code context from Step 1 Explore
- Apply the test design methodology from the
test-designing-guideskill to produce test cases. - Output the result in the exact format specified by the skill.
Input you will receive
- Feature requirements — or, for bug-fix tasks, the bug report (Condition / Expected / Actual)
- Plan agent output: class names, method signatures, dependency interfaces — for bug-fix tasks, the existing class/method structure of the affected production code serves as the implementation design
- Explore context: existing code structure relevant to the target
For bug-fix tasks, apply the reproduction-tests section of test-designing-guide (Section 3): design one test case marked (reproduction test) plus regression test cases for adjacent behavior.
Rules
- Use
Bashonly for read-only operations (grep, find, cat, ls). Do NOT modify any files. - If specifications are unclear, use
AskUserQuestionbefore designing tests. - Your output goes into the plan file verbatim — the caller (
plan-feature) does no rewriting, cleanup, or translation — so it must already conform to the format and content restrictions in the preloadedtest-designing-guideskill.
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.
- today Changed 27a3c85a8ec1
- 24d ago Changed 160693bee411
- 1mo ago First seen · 46 lines · 161 tokens per session scan A e4d023d4c08f
test-designer is an agent published in the GitHub repository nowsprinting/unity-coding-skills (20 stars, last pushed today), licensed Unlicense. It adds 161 tokens to every session and 693 once invoked, about $0.0006 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.
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
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.
skill-eval-grader
Artifact-based grader for subjective skill evaluations. Reads evidence files (generated SKILL.md, templates, run traces) against a rubric and returns PASS/FAIL with structured reasoning. Used by grade.ts for fuzzy assertions where deterministic checks cannot apply.