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/zackiles/cursor-mcp-manager/with-project-readmegit clone --depth 1 https://github.com/zackiles/cursor-mcp-managerWrote 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/zackiles/cursor-mcp-manager/with-project-readme)<a href="https://agentmods.dev/rules/zackiles/cursor-mcp-manager/with-project-readme"><img src="https://agentmods.dev/badge/rules/zackiles/cursor-mcp-manager/with-project-readme.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.00980 |
| Opus 5 | $0.00000 | $0.00490 |
| Sonnet 5 | $0.00000 | $0.00196 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
with-project-readme 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 5d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project README.md Content and Structure Guidelines
This rule provides guidance for maintaining and updating the README.md file, which serves as the primary documentation for the MCP Server Manager.
- Follow these guidelines when updating README.md
- Follow these guidelines to update README.md when major code changes that are DIRECTLY releated to the current documentation have made it out of date or innacurate.
ONLY FOR THE README.md IN THE PROJECT ROOT!
IMPORTANT: THESE GUIDELINES ONLY APPLY TO THE PROJECT README LOCATED AT THE PATH "{projectRoot}/README.md". IT DOES NOT APPLY TO OTHER FILES NAMED README.nd ELSEWHERE.
Core Purpose and Priorities
The README focuses exclusively on helping users understand and work with MCP servers through this manager. It should:
- Prioritize practical guidance for configuring and managing MCP servers
- Explain concepts in a user-centric way, avoiding implementation details
- Maintain clear section organization that follows a logical workflow
- Present instructions as step-by-step processes where appropriate
Required Sections (in this order)
- Project Overview
- Brief description of purpose (simplifying MCP server management)
- Getting started guide
- Server config goes in servers/
- Reference the server template file in mcp-atlassian.env.example and mcp-atlassian.ts.example
- Reference the optional but suggested option of the user forking this codebase and configuring their servers in it.
- Reference the optional choice of adding "src/mod.ts" aliased on their local PATH so they can access the CLI on their machine while working on other projects in the terminal to manage MCP servers. Alternatively they can create a Cursor rule in their projects that can manage the CLI and be provided the path to "src/mod.ts" so that an agent in any project can start and stop servers on its own.
- Explanation of what an MCP server is and why it matters
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.
- 5d ago First seen · 97 lines · 0 tokens per session scan A a03a598b1400
with-project-readme is a cursor rule published in the GitHub repository zackiles/cursor-mcp-manager (3 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 980 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-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.
family-instance-domain-actions
Family instance domain action implementation patterns.
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.