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/hamzaamjad/cursor-rulesWrote 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/hamzaamjad/cursor-rules/301-tooling-mcp-reference)<a href="https://agentmods.dev/rules/hamzaamjad/cursor-rules/301-tooling-mcp-reference"><img src="https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/301-tooling-mcp-reference/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/hamzaamjad/cursor-rules/301-tooling-mcp-reference"><img src="https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/301-tooling-mcp-reference.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.00008 | $0.00260 |
| Opus 5.5 | $0.00003 | $0.00104 |
| Sonnet 5.5 | $0.00002 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
301-tooling-mcp-reference 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
MCP Tool Reference
Desktop Commander
edit_block: Line-based precise edits
write_file: Full file write/append
read_file: Partial reads with offset
search_code: Regex with context lines
list_directory: File/dir enumeration
get_file_info: Metadata + line counts
GitHub MCP
create_pull_request: PR creation
push_files: Multi-file commits
search_repositories: Query repos
get_issue: Issue details
fork_repository: Fork to account
Perplexity MCP
perplexity_research: Deep research
perplexity_reason: Complex reasoning
perplexity_ask: Quick queries
Other MCP Servers
- HuggingFace: Model/dataset search, image generation
- Memory: Knowledge graph operations
- Sequential Thinking: Multi-step reasoning
- Time: Timezone conversions
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 · 44 lines · 8 tokens per session scan A c2315c1a1b35
301-tooling-mcp-reference is a cursor rule published in the GitHub repository hamzaamjad/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 8 tokens to every session and 260 once invoked, about $0.0000 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-31.
Other cursor rules, from other repositories
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).