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/pylarco/diff-apply/dry.strictgit clone --depth 1 https://github.com/pylarco/diff-applyWrote 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/pylarco/diff-apply/dry.strict)<a href="https://agentmods.dev/rules/pylarco/diff-apply/dry.strict"><img src="https://agentmods.dev/badge/rules/pylarco/diff-apply/dry.strict.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 | $0.00000 | $0.00422 |
| Opus 5 | $0.00000 | $0.00211 |
| Sonnet 5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
dry.strict 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 2d 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
description: If you are need to polish the code quality AFTER creating new tsx file. Read this rule globs: alwaysApply: false
You have to follow these rules:
Do:
- Strictly follow requirements
- Use functional programming techniques exclusively
- Maintain immutability throughout
- Use DRY principle across all files
- Always have bun-first mindset
- Always clean leftover unnecessary files
- Highly reusability
reactFC functions in SINGLE tsx file - Use Ver and Hor based structure on tsx file
- Within the nested ver hor, the last deepest child should use proper html semantic not div, ver hor
Don't:
- Do not use
tailwind.config.jsit is deprecated in Tailwind CSS v4. v4 only needs@import "tailwindcss";in the CSS file. - No DIV allowed, only use Ver Hor for directional component spreads
- Avoid OOP, classes, or inheritance
- Avoid traditional methods. use HOF
- Don't write // comments
- Don't use
anyorunknowntypes - Don't use JSX elements like , , , etc in the return statements, they should be extracted into separate functional FC components.
- No props drilling, use jotai
- use lucide react rather than writing svgs
- Do not create any new files other than these;
a.
src\components\page\*.page.tsx: b.src\components\ui\*.reuse.tsx: c.src\types\common.type.ts: d.src\types\props.type.ts: e.src\state-management\hooks\*.hook.ts: jotai useAtom f.src\state-management\hooks\*.state.ts: jotai atom
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.
- 2d ago First seen · 40 lines · 0 tokens per session scan A 1bb10e1e4a94
dry.strict is a cursor rule published in the GitHub repository pylarco/diff-apply (10 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 422 tokens. 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-09-02.
Other cursor rules, from other repositories
general
Wonder Blocks design system conventions, component patterns, and coding standards.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
new-component
Workflow for creating new React components.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
solana-transaction-safety
Safe Solana transaction submission patterns using Helius Sender.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.