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 agents/nowsprinting/unity-coding-skills/test-designergit clone --depth 1 https://github.com/nowsprinting/unity-coding-skillsWhat 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.00161 | $0.00726 |
| Opus 5 | $0.00081 | $0.00363 |
| Sonnet 5 | $0.00032 | $0.00145 |
| Haiku 4.5 | $0.00016 | $0.00073 |
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 yesterday.
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 MUST already conform to the format and content restrictions specified by the
test-designing-guideskill. The caller (plan-feature) will paste your Test Cases output verbatim into the plan file — no rewriting, cleanup, or translation will be performed on it. Ensure prohibited content (framework attributes, async/coroutine patterns, rationale text, etc.) is never present in your output.
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.
- yesterday 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 (19 stars, last pushed yesterday), licensed Unlicense. It adds 161 tokens to every session and 726 once invoked, about $0.0008 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-30.
Other agents, from other repositories
uss-bem-checker
Reviews USS stylesheets and the C# strings that reference them against the Aspid.FastTools BEM grammar (class names) and the positional grammar (custom properties). Use after edits to any .uss file or to any code holding USS class names / --aspid- variables (Constants.cs, AspidStyles.cs, component .cs files).
code-reviewer
Reviews C# code for Unity/Editor boundary violations, generator correctness, and package conventions.
unity-guide
Agent "unity-guide" from bigdra50/unity-cli, covering unity guide agent, ドメイン, 情報ソース, unity 公式ドキュメント and yaml 関連ドキュメント.
version-checker
Agent "version-checker" from bigdra50/unity-cli, covering version checker agent, 役割分担, 情報ソース, unity リリース情報 and バージョン命名規則.
code-simplifier
Use this agent when the user wants to simplify, refactor, or optimize existing code for better readability, maintainability, and performance. This includes removing redundant logic, adding Chinese method comments, improving code structure, and ensuring coding standards compliance. Examples:\n\n- User…
wiki-query-agent
Use this agent ONLY when explicitly instructed by a skill (e.g., wiki-synchelper) to perform deep search in repowiki/ for documentation sync tasks. Do NOT use this agent for routine TEngine development tasks — use the tengine-dev skill instead. This agent is NOT a general-purpose TEngine reference tool.