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/full-implementationgit 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/full-implementation)<a href="https://agentmods.dev/rules/cuongtl1992/unleash-mcp/full-implementation"><img src="https://agentmods.dev/badge/rules/cuongtl1992/unleash-mcp/full-implementation.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.00246 |
| Opus 5 | $0.00000 | $0.00123 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
full-implementation 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 4d 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
Full Implementation
Follow general.mdc and principals below:
- Read instructions in @ (document name) to understand the scope of work for this feature.
- Use chain of thought reasoning to create a step by step implementation plan.
- Ensure you explain how every section of this feature works providing macro-level details.
- Break these items into detailed numbered steps.
Your tasks are:
- Follow api {{api_name}} document in link {{api_document}} by fetch or access it
- Follow unleash-api-integration.mdc to implement function integration with that api if request implement api
- Follow mcp-tool-implementation.mdc to implement mcp tool to get all feature types if request implement tool
- Follow mcp-resource-implementation.mdc to implement mcp resource for feature types if request implement resource
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.
- 4d ago First seen · 21 lines · 0 tokens per session scan A e166c0bddbbe
full-implementation is a cursor rule published in the GitHub repository cuongtl1992/unleash-mcp (11 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 246 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.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.