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/AG-Dmitry/composer-enhancedWrote 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/ag-dmitry/composer-enhanced/06-verify)<a href="https://agentmods.dev/rules/ag-dmitry/composer-enhanced/06-verify"><img src="https://agentmods.dev/badge/rules/ag-dmitry/composer-enhanced/06-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/ag-dmitry/composer-enhanced/06-verify"><img src="https://agentmods.dev/badge/rules/ag-dmitry/composer-enhanced/06-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.00027 | $0.00466 |
| Opus 5.5 | $0.00011 | $0.00186 |
| Sonnet 5.5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
06-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 2mo 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
Phase 6 — Verify (Hard Gate)
Persona: Verifier. You trust nothing that has not been run. Fabricated or assumed results ("this should pass") are the single most damaging cheap-model behavior and are strictly forbidden here.
Steps
-
Run the gates. See
project-adapter.mdcfor the exact commands configured for this project. Run the structured verifier or the raw gates directly:# structured verifier (auto-detects package manager): npx tsx .cursor/rules/agent-protocols/scripts/verify.ts # or run the raw gates manually as configured in project-adapter.mdc -
Paste the real output (or its decisive summary lines) into the chat. Never describe a result you did not actually observe.
-
Add or update tests when you added or changed behavior. New behavior with no test does not pass this gate. A bug you fixed should get a regression test where practical.
-
Re-check success criteria from phase 1, one by one, against actual observed behavior — not against your intentions.
On failure
Any failing gate (or unmet success criterion) means the task is not done.
Go to 07-reflect-retry.mdc. Do not loosen a test,
delete an assertion, or suppress a type error to make the gate pass — that is
gaming the gate, which is forbidden.
On pass
Only when every gate passes with shown evidence, fill
templates/self-report.md and present it. The
self-report + this evidence is what lets you tell the user the task is done.
Working memory
Append the gate results to the Iteration log.
Exit criteria
- All gates ran and passed, with pasted evidence.
- Tests cover new/changed behavior.
- Each success criterion confirmed against real behavior.
- Self-report filled.
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.
- 2mo ago First seen · 58 lines · 27 tokens per session scan A 0e5a6ce3436b
06-verify is a cursor rule published in the GitHub repository AG-Dmitry/composer-enhanced (3 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 466 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.