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/KwokJay/cc-agent-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/kwokjay/cc-agent-harness/agent-review-and-verify)<a href="https://agentmods.dev/rules/kwokjay/cc-agent-harness/agent-review-and-verify"><img src="https://agentmods.dev/badge/rules/kwokjay/cc-agent-harness/agent-review-and-verify/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/kwokjay/cc-agent-harness/agent-review-and-verify"><img src="https://agentmods.dev/badge/rules/kwokjay/cc-agent-harness/agent-review-and-verify.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.00275 | $0.00275 |
| Opus 5 | $0.00138 | $0.00138 |
| Sonnet 5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
agent-review-and-verify 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 8d 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
任务完成门禁（必做）
在本仓库完成任意功能、修复或重构后，在宣称「完成」之前必须执行：
1. Agent 审查（自检）
- 对照本次改动的目标，通读 diff：是否有无关改动、遗漏边界情况、类型与安全风险。
- 确认对外行为（CLI 输出、生成文件路径、配置字段）与 README / CHANGELOG 意图一致。
- 若涉及用户可见文案或 breaking change，检查是否需更新文档。
2. 自动化验证
在仓库根目录执行（须全部通过）：
pnpm agent-review
等价于依次执行：pnpm lint → pnpm test → pnpm build。
若任一失败，不得合并或交付；修复后重新运行直至通过。
3. 与 CI 对齐
CI 使用相同门禁（见 .github/workflows/ci.yml）。本地通过 pnpm agent-review 后再推送，可减少 CI 失败轮次。
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.
- 8d ago First seen · 31 lines · 275 tokens per session scan A 034f0a477a50
agent-review-and-verify is a cursor rule published in the GitHub repository KwokJay/cc-agent-harness (2 stars, last pushed 5mo ago), licensed MIT. It adds 275 tokens to every session, about $0.0014 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
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-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.