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/LiuYihey/Agent-EngineeringWrote 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/liuyihey/agent-engineering/no-patches)<a href="https://agentmods.dev/rules/liuyihey/agent-engineering/no-patches"><img src="https://agentmods.dev/badge/rules/liuyihey/agent-engineering/no-patches/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/liuyihey/agent-engineering/no-patches"><img src="https://agentmods.dev/badge/rules/liuyihey/agent-engineering/no-patches.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.00279 | $0.00279 |
| Opus 5.5 | $0.00112 | $0.00112 |
| Sonnet 5.5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
no-patches 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 1mo 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
No Patches - Root-Cause Fixes Only
When something breaks or behaves wrong, fix the source (state model, prompt scope, persistence, tool policy). Do not paper over symptoms.
Avoid
- Keyword/regex routing when the agent or UI already has conversation history and session state.
- Dedupe, strip, trim, or merge logic whose job is to hide duplicate or wrong model output.
- Forced tool calls or special-case branches that compensate for unclear prompts or missing context.
- One-off examples or phrase lists embedded in prompts or code paths.
Prefer
- Facts over inference rules: inject what the system knows; let the model or UI interpret the transcript.
- Structural constraints: disable tools, phases, or code paths that should not run - not "please don't" in prose.
- Single ownership: each artifact (plan, summary, segment) is produced once in the right layer; align server persistence with client rendering.
- Prompt scope: if output is wrong or repeated, tighten role and phase boundaries (see
concise-agent-promptsskill).
If a fix only works for one utterance, one screen, or one failure mode, redesign instead of extending the patch.
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.
- 1mo ago First seen · 25 lines · 279 tokens per session scan A 729a252733ea
no-patches is a cursor rule published in the GitHub repository LiuYihey/Agent-Engineering (5 stars, last pushed 2mo ago), licensed MIT. It adds 279 tokens to every session, about $0.0011 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
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.