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/08-gotchas-verification)<a href="https://agentmods.dev/rules/alieismy/codex-three-layer-delivery/08-gotchas-verification"><img src="https://agentmods.dev/badge/rules/alieismy/codex-three-layer-delivery/08-gotchas-verification.svg" alt="Measured on agentmods" 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.00340 | $0.00340 |
| Opus 5 | $0.00170 | $0.00170 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
08-gotchas-verification 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 7d 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
Gotchas And Verification
Gotchas Log
Record recurring failure patterns when they create real risk. A gotcha entry should include:
### YYYY-MM-DD: Short title
- Problem: What happened
- Symptom: How it was discovered
- Fix: How it was resolved
- Prevention: How to avoid recurrence
Promotion Rule
- If the same gotcha appears three or more times, promote it into a formal rule or skill update.
- If a gotcha has not appeared for more than 30 days and is no longer useful, consider archiving it.
- Link gotchas to the skill or workflow that can prevent recurrence.
Verification Discipline
For every document, standards, or configuration change:
- Identify the expected behavior.
- Run the closest configured verification command or document consistency check.
- If verification cannot be run, state the reason.
- Report residual risk separately.
Final Reporting Checklist
Final responses should include the highest-signal facts:
- What changed.
- What was verified.
- What was not verified.
- Any residual risks or follow-up work.
Avoid burying verification results under long narration.
Diff Hygiene
- Keep diffs scoped to the task.
- Re-read changed files before finishing. Inspect the final diff for missed references, accidental coupling, duplicated logic, unrelated formatting, generated noise, local-only paths, and suspected secrets.
- Run whitespace and syntax checks when the repository provides them.
- Do not revert unrelated user changes.
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.
- 7d ago First seen · 52 lines · 340 tokens per session scan A 4fb99d38ba71
08-gotchas-verification is a cursor rule published in the GitHub repository alieismy/codex-three-layer-delivery (2 stars, last pushed 7d ago), licensed MIT. It adds 340 tokens to every session, about $0.0017 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
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
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.
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.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.