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-my-teamgit 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-my-team)<a href="https://agentmods.dev/rules/zackiles/cursor-mcp-manager/with-my-team"><img src="https://agentmods.dev/badge/rules/zackiles/cursor-mcp-manager/with-my-team.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.1 | $0.00000 | $0.00479 |
| Opus 5 | $0.00000 | $0.00239 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
with-my-team 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 6d 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
Context for MCP Tool Calls
Before making tool calls with MCP first review the files in the context/ folder which provides context on who I am, my team, my department, and my company. It will provide valuable details in order to craft your tool calls with the right arguments.
Examples of Context
All of these things could potentially be in a file in the context/ folder.
- Names of colleagues
- Emails of colleagues
- Jira
- Boards
- Tickets
- Project Keys
- Terms to search within tickets
- Names or emails or usernames or user IDs of colleagues
- Names of teams
- Names of projects
- ...
- Confluence
- Spaces
- Page IDs
- Terms to search within pages
- Names or emails or usernames or user IDs of colleagues
- Names of teams
- Names of projects
- ...
- Google Drives
- Folder names
- File names
- Terms to search within files
- Names or emails or usernames or user IDs of colleagues
- Names of teams
- Names of projects
- ...
- Github
- Org names
- Repositories
- Usernames
- Groups
- Applications, Services, and Systems
- Names of these typically map 1:1 for repositories on Github under the company's github Org name e.g
https://github.com/{Github Org Name}/some-service-name
- Names of these typically map 1:1 for repositories on Github under the company's github Org name e.g
- Slack
- Channel IDs
- Usernames
- Groups
- Colleagues to check DMs with
Examples of User Queries That Benefit From Context
Finding Jira Tickets
USER QUERY: List all Jira tickets for my teams which are blocked and have been updated in the last month.
SEARCH context/ FOR:
- Their team's Project Keys
CONTEXT FOUND:
- Project Keys: PROJA, PROJB, PROJC
MCP TOOL CALL WITH CONTEXT:
{
"jql": "status = \"Blocked / On hold\" AND updated >= -30d AND (project IN (PROJA, PROJB, PROJC)) ORDER BY updated DESC",
"limit": 50
}
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.
- 6d ago First seen · 71 lines · 0 tokens per session scan A dcfd801bcd8e
with-my-team 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 479 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
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.
cli-error-handling
CLI command error handling 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.