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/alieismy/codex-three-layer-deliveryWrote 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/alieismy/codex-three-layer-delivery/06-quality-gates)<a href="https://agentmods.dev/rules/alieismy/codex-three-layer-delivery/06-quality-gates"><img src="https://agentmods.dev/badge/rules/alieismy/codex-three-layer-delivery/06-quality-gates/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/alieismy/codex-three-layer-delivery/06-quality-gates"><img src="https://agentmods.dev/badge/rules/alieismy/codex-three-layer-delivery/06-quality-gates.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.00568 | $0.00568 |
| Opus 5 | $0.00284 | $0.00284 |
| Sonnet 5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
06-quality-gates 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Gates
Before completing requirements, feasibility, research, design, standards, or review work, confirm:
- Key conclusions are supported by evidence.
- Facts, assumptions, estimates, inferences, and unknowns are separated.
- Relevant boundary conditions, compliance constraints, and risks are covered.
- Unconfirmed points are listed with verification actions.
- Verification actions and results are recorded.
- Match verification scope to change risk and blast radius. Start with the minimum sufficient checks directly relevant to the change, and broaden verification for shared behavior, cross-module contracts, security-critical paths, or build and release contracts. Do not skip necessary checks to save time or run expensive repository-wide checks without justification.
- Sequence verification from low-cost preflight to changed-surface evidence and related regression. Reserve a full behavior or platform matrix for shared routing, public contracts, release decisions, an observed cross-surface risk, or an explicit user request.
Skill-Specific Gates
| Work type | Minimum quality gate |
|---|---|
/rd-requirement |
Core scenarios covered; priorities, assumptions, exclusions, acceptance criteria, and traceability explicit |
/rd-feasibility |
Decision question clear; dimensions covered; options compared; conclusion, confidence, conditions, risks, and verification actions explicit |
/rd-research |
Mode, source authority, date/version/environment, applicability, reproducibility, counterevidence, confidence, gaps, and downstream usage are explicit |
/rd-solution |
Candidate comparison and recommendation rationale clear; architecture, security, cost, risk, and exit path addressed |
/rd-design |
Interfaces, data models, critical flows, failure paths, trust boundaries, security, auditability, concurrency, and unresolved decisions specified |
/rd-specification |
Clause-level evidence, normative wording, terminology, references, conflicts, and human-verification gaps handled |
/rd-writing |
Audience, purpose, claim architecture, evidence, counterargument, limitations, and conclusion boundary are explicit |
/rd-review |
Alignment/evidence and intrinsic-quality/argument assessed; findings include location, evidence, impact, severity rationale, and action; verdict follows unresolved impact |
/rd-delivery |
Explicit request confirmed; artifact paths, statuses, authority layers, dependencies, machine or human gates, waivers, re-review triggers, authoritative pointers, verification, and durable handoff are current; only required specialist Skills are invoked |
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.
- 4d ago Changed · +1 lines · +47 tokens per session 8bc95420694b
- 8d ago First seen · 41 lines · 521 tokens per session scan A 74a88635a9ca
06-quality-gates is a cursor rule published in the GitHub repository alieismy/codex-three-layer-delivery (2 stars, last pushed yesterday), licensed MIT. It adds 568 tokens to every session, about $0.0028 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
shard-doc
BMAD CORE Tool: Shard Document.
citazioni
Citazioni corrette (stile numerico) e bibliografia coerente per tesi triennale in LaTeX.
sigma-reports
Build, validate, retrieve, and safely update Sigma report code representations through /v2/reports/spec. Use for fixed-layout or pixel-perfect reports, invoices, statements, regulatory documents, and PDF delivery. Covers report pages, absolute pixel layout, header/footer panels, common elements, verification…
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.