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/4regab/agent-rules-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/4regab/agent-rules-mcp/test-mdc)<a href="https://agentmods.dev/rules/4regab/agent-rules-mcp/test-mdc"><img src="https://agentmods.dev/badge/rules/4regab/agent-rules-mcp/test-mdc/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/4regab/agent-rules-mcp/test-mdc"><img src="https://agentmods.dev/badge/rules/4regab/agent-rules-mcp/test-mdc.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.00059 | $0.00059 |
| Opus 5.5 | $0.00024 | $0.00024 |
| Sonnet 5.5 | $0.00012 | $0.00012 |
| Haiku 4.5 | $0.00006 | $0.00006 |
Grade A, and why
test-mdc 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 1mo 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
Test MDC Rules
This is a test MDC file to reproduce the issue with .mdc files not being fetched.
Key Points
- This should be discoverable by list_rules
- This should be fetchable by get_rules
- MDC files should work the same as .md files
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.
- 1mo ago First seen · 8 lines · 59 tokens per session scan A 9b91fcaad2bd
test-mdc is a cursor rule published in the GitHub repository 4regab/agent-rules-mcp (13 stars, last pushed 1y ago), licensed MIT. It adds 59 tokens to every session, about $0.0002 per session on Opus 5.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-30.
Other cursor rules, from other repositories
cursor_conductor_task_management
description: Best practices for effective task management with Conductor Tasks in an AI-assisted workflow globs: / alwaysApply: true.
guide-for-using-mcp-servers
Helps organize thoughts, break down problems, and build reasoning step by step.
coding_practices-documentation-jsdoc
Cursor rule "coding_practices-documentation-jsdoc" from PerkyZZ999/MemorizedMCP, covering codingpractices and guidelines for documentation.
music-mcp-rules
Cursor rule "music-mcp-rules" from gorums/music-mcp-server, covering 🔄 project awareness & context, 🧱 code structure & modularity, 🧪 testing & reliability, ✅ task completion and 📎 style & conventions.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.