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/visionTw/godot-ai-harnessWrote 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/rules/visiontw/godot-ai-harness/post-change-runtime-check)<a href="https://agentmods.dev/rules/visiontw/godot-ai-harness/post-change-runtime-check"><img src="https://agentmods.dev/badge/rules/visiontw/godot-ai-harness/post-change-runtime-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.1 | $0.00184 | $0.00184 |
| Opus 5 | $0.00092 | $0.00092 |
| Sonnet 5 | $0.00037 | $0.00037 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
post-change-runtime-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 6d 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
Post Change Runtime Check
- 当改动涉及
scripts/、scenes/、resources/、输入链路或布局参数时，必须触发一次运行验证。 - 运行验证优先顺序：
- 启动检查（项目可启动，无崩溃）
- smoke 检查（关键路径）
- 必要时执行打包检查（平台相关改动）
- 在可行情况下，优先“直接运行验证”而不是导出预览帧。
- 每次验证都应输出可追溯证据（命令、结果、关键日志）。
- 如果验证失败，先修复阻断问题，再继续文档回写或发布动作。
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.
- 6d ago First seen · 16 lines · 184 tokens per session scan A b813283fac64
post-change-runtime-check is a cursor rule published in the GitHub repository visionTw/godot-ai-harness (2 stars, last pushed 19d ago), licensed MIT. It adds 184 tokens to every session, about $0.0009 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 cursor rules, from other repositories
unity-testing
Unity Test Framework (Production Standards).
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.