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/DevEngageLab/engagelab-sms-mcpWrote 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/devengagelab/engagelab-sms-mcp/readme-sync-after-code-update)<a href="https://agentmods.dev/rules/devengagelab/engagelab-sms-mcp/readme-sync-after-code-update"><img src="https://agentmods.dev/badge/rules/devengagelab/engagelab-sms-mcp/readme-sync-after-code-update/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/devengagelab/engagelab-sms-mcp/readme-sync-after-code-update"><img src="https://agentmods.dev/badge/rules/devengagelab/engagelab-sms-mcp/readme-sync-after-code-update.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.00171 | $0.00171 |
| Opus 5 | $0.00086 | $0.00086 |
| Sonnet 5 | $0.00034 | $0.00034 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
readme-sync-after-code-update 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 8d 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
README Sync Requirement
After every code update, verify whether README.md needs to be updated.
Mandatory Steps
- Compare the code change against current README content.
- Check whether usage, setup, configuration, APIs, scripts, env vars, or examples changed.
- If README is outdated or incomplete, update it in the same task.
- Keep README changes specific, accurate, and aligned with the final implementation.
- Before finishing, confirm either:
- README update completed, or
- no README change is required (and briefly state why).
Quick Checklist
- Did behavior or features change?
- Did command/config/env usage change?
- Did interfaces or examples change?
- If yes to any item, update
README.mdnow.
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.
- 8d ago First seen · 26 lines · 171 tokens per session scan A f951372e9e46
readme-sync-after-code-update is a cursor rule published in the GitHub repository DevEngageLab/engagelab-sms-mcp (0 stars, last pushed 5mo ago), licensed MIT. It adds 171 tokens to every session, about $0.0009 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
about-codebase
General information about the Lineai MCP Server codebase and its purpose.
toc-readme
When updating README.md, the table of contents should contain only the second-level headings below it.
runwhen-infrastructure
Infrastructure conventions for scripts targeting Kubernetes and databases via RunWhen runners.
php-client-implementation
Guidelines for implementing MCP clients in PHP.
cursor_rules
Guidelines for creating and maintaining Cursor rules to ensure consistency and effectiveness.
validate-design-early
Ask for design approval before implementing 100+ lines.