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/mondweep/remote-mcp-creation-foundation/apply-diff-guidelinesgit clone --depth 1 https://github.com/mondweep/remote-mcp-creation-foundationWrote 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/mondweep/remote-mcp-creation-foundation/apply-diff-guidelines)<a href="https://agentmods.dev/rules/mondweep/remote-mcp-creation-foundation/apply-diff-guidelines"><img src="https://agentmods.dev/badge/rules/mondweep/remote-mcp-creation-foundation/apply-diff-guidelines.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.00005 | $0.00294 |
| Opus 5 | $0.00003 | $0.00147 |
| Sonnet 5 | $0.00001 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
apply-diff-guidelines 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 3d 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
Preventing apply_diff Errors
CRITICAL: When using apply_diff, never include literal diff markers in your code examples
CORRECT FORMAT for apply_diff:
<apply_diff>
<path>file/path.js</path>
<diff>
<<<<<<< SEARCH
// Original code to find (exact match)
=======
// New code to replace with
>>>>>>> REPLACE
</diff>
</apply_diff>
COMMON ERRORS to AVOID:
- Including literal diff markers in code examples or comments
- Nesting diff blocks inside other diff blocks
- Using incomplete diff blocks (missing SEARCH or REPLACE markers)
- Using incorrect diff marker syntax
- Including backticks inside diff blocks when showing code examples
When showing code examples that contain diff syntax:
- Escape the markers or use alternative syntax
- Use HTML entities or alternative symbols
- Use code block comments to indicate diff sections
SAFE ALTERNATIVE for showing diff examples:
// Example diff (DO NOT COPY DIRECTLY):
// [SEARCH]
// function oldCode() {}
// [REPLACE]
// function newCode() {}
ALWAYS validate your diff blocks before executing apply_diff
- Ensure exact text matching
- Verify proper marker syntax
- Check for balanced markers
- Avoid nested markers
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.
- 3d ago First seen · 49 lines · 5 tokens per session scan A b4c8acbb6431
apply-diff-guidelines is a cursor rule published in the GitHub repository mondweep/remote-mcp-creation-foundation (0 stars, last pushed 1y ago), licensed MIT. It adds 5 tokens to every session and 294 once invoked, about $0.0000 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
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.