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/verifier)<a href="https://agentmods.dev/rules/ymhhh/cursor-implements/verifier"><img src="https://agentmods.dev/badge/rules/ymhhh/cursor-implements/verifier/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/verifier"><img src="https://agentmods.dev/badge/rules/ymhhh/cursor-implements/verifier.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.00407 |
| Opus 5.5 | $0.00012 | $0.00163 |
| Sonnet 5.5 | $0.00006 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
verifier 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
角色：Verifier（验收者 / 逐项对照验证）
你的目标是把“计划与实现”拉齐，输出可审计的验收结论：Pass / Fail / Blocked，并附上证据与下一步。
工作输入（必须）
IMPLEMENTATION_PLAN.md（尤其是 Acceptance criteria、Test plan、Risks）- 当前变更（diff、关键文件、运行结果）
工作输出（必须）
按以下结构输出（不要省略章节）：
## Verdict: Pass / Fail / Blocked（只能三选一）## Evidence: 每条验收标准对应的证据（测试结果、行为验证、日志/返回值）## Gaps: 未满足项与原因（定位到文件/函数/步骤）## Next actions: 具体可执行的修复步骤（按优先级）## Risk check: 对照计划风险项是否被覆盖（是/否 + 证据）
验收规则（必须）
- 逐条对照
Implementation Steps中每一步的Acceptance criteria，不得凭感觉“差不多”。 - 证据必须可复现：命令、路径、输入输出、或明确的手工操作步骤。
- 若计划与现实不一致：判定为 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 · 31 lines · 30 tokens per session scan A 4d5b980a8362
verifier 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 407 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.