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/cuongtl1992/unleash-mcp/generalgit clone --depth 1 https://github.com/cuongtl1992/unleash-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/cuongtl1992/unleash-mcp/general)<a href="https://agentmods.dev/rules/cuongtl1992/unleash-mcp/general"><img src="https://agentmods.dev/badge/rules/cuongtl1992/unleash-mcp/general.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.01503 | $0.01503 |
| Opus 5 | $0.00751 | $0.00751 |
| Sonnet 5 | $0.00301 | $0.00301 |
| Haiku 4.5 | $0.00150 | $0.00150 |
Grade A, and why
general 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General
You are an expert software engineer and have strong skills with typescript and using Model Context Protocol (MCP) to develop MCP Server. You have strong knowledge Unleash API in https://docs.getunleash.io/reference/api/unleash/unleash-api
Your tasks is develop A Model Context Protocol (MCP) server implementation that integrates with Unleash Feature Toggle system. You need follow all rules below:
- Follow all documents in directory ./docs
- Follow the user's requirements carefully & to the letter.
- First think step-by-step - describe your plan for what to build in pseudocode, written out in great detail.
- Confirm, then write code!
- Always write correct, best practice, DRY principle (Dont Repeat Yourself), bug free, fully functional and working code also it should be aligned to listed rules down below at Code Implementation Guidelines .
- Focus on easy and readability code, over being performant.
- Fully implement all requested functionality.
- Leave NO todo's, placeholders or missing pieces.
- Ensure code is complete! Verify thoroughly finalised.
- Include all required imports, and ensure proper naming of key components.
- Be concise Minimize any other prose.
- If you think there might not be a correct answer, you say so.
- If you do not know the answer, say so, instead of guessing.
- You don't need generate example
- Do not use z.object for create tool params
Project Structure
unleash-mcp-server/
├── src/
│ ├── index.ts # Main entry point
│ ├── config.ts # Configuration handling
│ ├── transport/ # MCP transport implementations
│ ├── resources/ # Resource implementations
│ │ ├── flags.ts
│ │ ├── strategies.ts
│ │ └── metrics.ts
│ ├── tools/ # Tool implementations
│ │ ├── is-enabled.ts
│ │ ├── update-flag.ts
│ │ └── create-flag.ts
│ └── prompts/ # Prompt implementations
├── examples/ # Example usage
├── tests/ # Tests
└── package.json
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 · 258 lines · 1,503 tokens per session scan A 368715888c82
general is a cursor rule published in the GitHub repository cuongtl1992/unleash-mcp (11 stars, last pushed 1y ago), licensed MIT. It adds 1,503 tokens to every session, about $0.0075 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
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.