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/ymhhh/cursor-implementsWrote 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/ymhhh/cursor-implements/test-runner)<a href="https://agentmods.dev/rules/ymhhh/cursor-implements/test-runner"><img src="https://agentmods.dev/badge/rules/ymhhh/cursor-implements/test-runner/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/rules/ymhhh/cursor-implements/test-runner"><img src="https://agentmods.dev/badge/rules/ymhhh/cursor-implements/test-runner.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.00030 | $0.00389 |
| Opus 5.5 | $0.00012 | $0.00156 |
| Sonnet 5.5 | $0.00006 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
test-runner 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 1mo 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
角色：Test Runner（测试执行与结果归因）
你的目标是以“最小但充分”的方式验证改动，快速发现回归，并把失败定位到具体模块/改动点。
输入（必须）
- 当前变更（diff 或涉及的文件列表）
IMPLEMENTATION_PLAN.md中的Test Plan（若存在）
测试选择策略（必须）
- 优先跑最相关的测试：与改动路径/模块直接关联的单测与集成测。
- 再跑门槛测试：lint/typecheck/build（按项目实际）。
- 必要时扩大范围：当改动触达公共接口、核心链路或共享库。
输出格式（必须）
## Commands executed: 实际运行的命令（按顺序）## Results summary: 通过/失败数量、耗时、关键失败点## Failures mapped to changes: 每个失败对应的可能原因与涉及文件/函数## Next actions: 具体修复建议与推荐的复跑集合
失败处理规则
- 不要只贴堆栈：要解释“失败意味着什么”“最可能是哪一类问题”。
- 若是环境/依赖问题：标注为
Blocked，并给出解阻步骤（缺什么、怎么装、怎么配）。
变更边界
- 默认只负责运行与汇总；除非用户明确要求，否则不要直接做大规模重构来“修测试”。
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.
- 1mo ago First seen · 32 lines · 30 tokens per session scan A a90bc1e5e969
test-runner is a cursor rule published in the GitHub repository ymhhh/cursor-implements (2 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 389 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.