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/yangfch3/unity-mcp-server/spec-post-checknpx skills add yangfch3/Unity-MCP-Server --skill spec-post-checkgit clone --depth 1 https://github.com/yangfch3/Unity-MCP-ServerWrote 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/skills/yangfch3/unity-mcp-server/spec-post-check)<a href="https://agentmods.dev/skills/yangfch3/unity-mcp-server/spec-post-check"><img src="https://agentmods.dev/badge/skills/yangfch3/unity-mcp-server/spec-post-check.svg" alt="Measured on agentmods" 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 | $0.00113 | $0.00601 |
| Opus 5 | $0.00056 | $0.00300 |
| Sonnet 5 | $0.00023 | $0.00120 |
| Haiku 4.5 | $0.00011 | $0.00060 |
Grade A, and why
spec-post-check 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Post-Processing Workflow
When the user expresses the intent for "Spec post-processing", execute the following checks.
Step 1: Spec Document Consistency Check
Read requirements.md, design.md, and tasks.md from the current Spec directory. Compare against the actually implemented code and check:
- Whether requirements added/modified during subsequent iterations have been synced to requirements.md
- Whether interfaces, data models, and correctness properties added/modified during subsequent iterations have been synced to design.md
- Whether implementation tasks and test tasks added/modified during subsequent iterations have been synced to tasks.md
If inconsistencies are found, execute updates directly.
Step 2: Steering Update Check
Determine whether the Spec's content involves framework-level changes (e.g., adding/modifying Frame Core, adding public utilities, changing key conventions, etc.).
- If framework-level changes: check whether files under
.kiro/steering/(e.g.,product.md,structure.md,tech.md) need to be updated. If so, execute directly. - If not framework-level changes (pure business logic, UI panels, etc.): skip, no steering update needed.
Step 3: README Update Check
Determine whether the Spec added/modified user-visible features (e.g., new tools, new APIs, changed configuration methods, etc.).
- If user-visible feature changes are involved: check whether
README.mdandREADME_EN.mdin the project root need to be updated (e.g., tool list, usage instructions, configuration instructions). If so, execute directly. - If only internal refactoring or changes that don't affect user usage: skip, no README update needed.
Step 4: CONTRIBUTING Update Check
Determine whether the Spec's changes affect contributor-facing content (e.g., project structure changes, new coding conventions, new test patterns, build process changes, etc.).
- If contributor-facing content is affected: check whether
CONTRIBUTING.mdandCONTRIBUTING_EN.mdneed to be updated. If so, execute directly. - If changes don't affect the contributor workflow: skip, no CONTRIBUTING update needed.
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.
- 4d ago First seen · 45 lines · 113 tokens per session scan A dbc9a9fec63d
spec-post-check is a skill published in the GitHub repository yangfch3/Unity-MCP-Server (6 stars, last pushed 2d ago), licensed MIT. It adds 113 tokens to every session and 601 once invoked, about $0.0006 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
dotcraft-unity
Use when dotcraft-unity MCP or unityexecutecsharp is available, or when the user asks to inspect, automate, capture, or debug Unity Editor state, scenes, assets, Console logs, or GameView output. Provides background-first Unity Editor automation rules.
jahro-logging
Reviews and improves Debug.Log usage in Unity C# projects following structured logging principles: context tags, severity contracts, boundary-based placement, and criticality tiers. Detects common antipatterns (naked Debug.Log, logging in Update, stringly-typed errors), adds missing logs at system/state/error/external…
jahro-migration
Analyzes existing debug systems (IMGUI menus, custom loggers, cheat frameworks, performance HUDs) and generates incremental migration plans to Jahro equivalents. Use when the user wants to replace a custom debug UI, migrate from an existing console or cheat system, switch to Jahro, or has OnGUI debug code they want to…
jahro-troubleshooting
Diagnoses common Jahro issues using decision trees: commands not appearing, watcher not updating, console not opening, snapshots failing, launch button missing. Use when the user reports something not working, missing, broken, or unexpected with Jahro, or when generated Jahro code doesn't behave as expected.
jahro-commands
Analyzes C# classes and generates [JahroCommand] attributes with correct syntax, RegisterObject patterns, and group organization. Use when the user wants to add runtime commands, cheats, or debug actions to Unity classes, or mentions JahroCommand, console commands, runtime cheats, or debug actions.
jahro-watcher
Analyzes C# fields and properties and generates [JahroWatch] attributes with groups and performance-safe patterns. Use when the user wants to monitor variables at runtime, add watchers, track game state, replace Debug.Log polling, or mentions JahroWatch, real-time inspection, or variable monitoring.