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/tecnomanu/pampa/readme-syncgit clone --depth 1 https://github.com/tecnomanu/pampaWrote 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/tecnomanu/pampa/readme-sync)<a href="https://agentmods.dev/rules/tecnomanu/pampa/readme-sync"><img src="https://agentmods.dev/badge/rules/tecnomanu/pampa/readme-sync.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.00690 |
| Opus 5 | $0.00000 | $0.00345 |
| Sonnet 5 | $0.00000 | $0.00138 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
readme-sync 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
README Synchronization Rule
Purpose
This rule ensures that both README.md and README_es.md files are kept synchronized with the same content, only in their respective languages.
Requirements
Content Parity
- Both README files must have identical structure and sections
- All features, version numbers, and technical information must be the same
- Only the language should differ between the files
Version Consistency
- Version numbers in headers must match exactly
- Feature lists and "What's New" sections must have equivalent content
- All technical specifications must be identical
Structure Matching
- Section headers must correspond (e.g., "🌟 What's New" ↔ "🌟 Novedades")
- Table of contents must have equivalent entries
- Code examples and commands should be identical
- Links and references must point to the same resources
Language Guidelines
- README.md: English content
- README_es.md: Spanish content
- Technical terms may remain in English when appropriate (e.g., "MCP", "Node.js")
- Commands and code blocks should remain identical
When Making Changes
To English README (README.md):
- Make your changes to the English version first
- Immediately update the Spanish version (README_es.md) with equivalent content
- Ensure version numbers and technical details match exactly
To Spanish README (README_es.md):
- If changes are made to Spanish version, ensure English version is updated
- Maintain consistency in technical information
- Keep the same structure and organization
Version Updates:
- Always update version numbers in both files simultaneously
- Feature announcements must be translated and included in both versions
- Performance metrics and technical specifications must match
Quality Checklist
Before committing changes to either README:
- Version numbers match in both files
- "What's New" sections have equivalent content
- Table of contents corresponds between languages
- All technical specifications are identical
- Code examples and commands are the same
- Links and references work in both versions
- Structure and organization match
- Both files are complete and well-formatted
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.
- 4d ago First seen · 107 lines · 0 tokens per session scan A 34f14198ac5e
readme-sync is a cursor rule published in the GitHub repository tecnomanu/pampa (30 stars, last pushed 11mo ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 690 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-08-30.
Other cursor rules, from other repositories
internationalization
Cursor rule "internationalization" from dtyq/magic, covering internationalization (i18n) rules, 国际化基本规范, 1. 文件结构, 2. 命名空间规范 and 3. 组件中使用国际化.
cmd-moodle-mustache-lint
Lint Mustache templates for accessibility, security, hard-coded strings, and Moodle template conventions. (invoke by typing: @moodle-mustache-lint).
uninettuno-monografia
Regole UNINETTUNO per tesi TRIENNALE in italiano, con termini tecnici inglesi ammessi.
controlflow-docs-evals
Rules for documentation parity, localized tutorials, and eval verification.
report
보고서를 작성할 때 참고하세요.
frontend-translation-management
Maintain consistent translation practices across the frontend application to ensure proper internationalization and user experience.