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 rules/david405/harness-kit/post-execute-reviewgit clone --depth 1 https://github.com/David405/harness-kitWhat 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.00317 | $0.00317 |
| Opus 5 | $0.00159 | $0.00159 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
post-execute-review 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 yesterday.
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-execute review
After a sprint contract is executed and VERIFY is green, run a harness review before staging product files or telling the human the work is complete.
Required order
CONTRACT (approved) → EXECUTE → VERIFY → REVIEW → stage → stop
- VERIFY — run the contract's verify commands; all must pass (or document skips with reason).
- REVIEW — read
harness-reviewskill +templates/REVIEW.md; grade against the contract. - Report — deliver the review summary to the human in chat (merge recommendation, findings). Do not paste harness review or contract compliance into the GitHub PR body.
- Stage — stage product files; set
FEATURES.jsontoPENDING_REVIEWif not already. - Stop — do not commit, push, or open a PR unless explicitly asked.
Not a substitute for human PASS
The executor runs review and sets PENDING_REVIEW. PASS is human-only after they approve merge.
When review can be skipped
- Trivial one-line fixes with no contract (if
AGENTS.mdallows condensed work) - Human explicitly says "skip review" for this session
Otherwise: no staging, no "done" message without review.
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.
- yesterday First seen · 35 lines · 317 tokens per session scan A 67608cc8e6c8
post-execute-review is a cursor rule published in the GitHub repository David405/harness-kit (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 317 tokens to every session, about $0.0016 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
test-plan
Plan Katalon True Platform/TestOps testing for a release, sprint, or feature. Use when you need to translate quality goals into scope, prioritize testing by requirement coverage and risk, decide what to test first, or build the executable plan structure (folders, suites, and sprint/release association) that stands in…
cli-forge-schema
Generate GitHub-compatible Mermaid diagrams — auto-picks diagram type, splits complex ones, converts tables/kanban/PERT.
STAGE_S5_TEST_POINTS
AIDocxWorkFlow Stage 5 — 测试点生成（独立阶段）.
sprint-planning
BMAD BMM Agent: sprint-planning.
head-of-product
Head of Product persona — planning, user stories, UX decisions, scope guardian. Use when discussing product strategy, PRDs, user research, feature proposals, or backlog prioritization.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.