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/integration.taskgit 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/integration.task)<a href="https://agentmods.dev/rules/pylarco/diff-apply/integration.task"><img src="https://agentmods.dev/badge/rules/pylarco/diff-apply/integration.task.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.00153 | $0.00153 |
| Opus 5 | $0.00077 | $0.00077 |
| Sonnet 5 | $0.00031 | $0.00031 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
integration.task 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
Analyze *.hook.ts files and the relevant Drizzle schemas. because some hook still not integrated with service
- Create/modify [singular_table_name].service.ts files providing CRUD for Drizzle tables, as required by existing hooks. the file name [name].service.ts should match drizzle table name.
- Refactor *.hook.ts to use these services for data fetching, mutation, and subscription.
- Ensure hooks correctly manage state (null,loading, data, error) from service responses.
- Modify Drizzle schemas as needed to optimize this database integration.
- Use HOF and immutability
- make sure to produce production ready code.
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 · 13 lines · 153 tokens per session scan A d1f8839999ab
integration.task is a cursor rule published in the GitHub repository pylarco/diff-apply (10 stars, last pushed 1y ago), licensed MIT. It adds 153 tokens to every session, about $0.0008 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-09-02.
Other cursor rules, from other repositories
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
query-optimization
查詢優化、EXPLAIN、index 設計與 RLS 效能測量.
sqlmodel
Satisfying the type checker when working with SQLModel.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.