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/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/unleash-api-integration)<a href="https://agentmods.dev/rules/cuongtl1992/unleash-mcp/unleash-api-integration"><img src="https://agentmods.dev/badge/rules/cuongtl1992/unleash-mcp/unleash-api-integration.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.00503 |
| Opus 5 | $0.00000 | $0.00251 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
unleash-api-integration 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 8d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unleash API Integration Guidelines
When implementing new Unleash API integrations, follow these consistent patterns to maintain code quality and readability:
File Structure
- Place all Unleash API integrations in the
src/unleash/directory - Use kebab-case for filenames (e.g.,
get-all-projects.ts,update-feature-toggle.ts) - Name files according to their primary function
Implementation Pattern
- Import the Unleash client:
import { client } from "./unleash-client.js";
- Create and export an async function with descriptive name:
export async function functionName(parameters): Promise<ReturnType | null> {
try {
const response = await client.METHOD('/api/admin/endpoint');
return response.data.specificProperty || response.data;
} catch (error) {
console.error('Error message:', error);
return null;
}
}
- Use proper JSDoc comments:
/**
* Brief description of what this function does
* @param paramName Description of parameter
* @returns Description of return value or null if unavailable
*/
-
When making requests:
- Use HTTP methods (get, post, put, delete) directly from the client
- Follow Unleash API endpoints from documentation at https://docs.getunleash.io/reference/api/unleash/unleash-api
- Handle response data properly, accounting for possible response structures
- Implement proper error handling with descriptive error messages
-
For POST/PUT requests, follow this pattern:
const response = await client.post('/api/admin/endpoint', {
property1: value1,
property2: value2
});
- Use proper TypeScript types:
- Define interfaces for request/response data
- Use specific return types rather than
anywhen possible - Consider using Zod for runtime validation when necessary
Testing
- Write unit tests for each API integration
- Mock the Axios client responses in tests
- Test both success and error scenarios
Error Handling
- Always wrap API calls in try/catch blocks
- Log informative error messages
- Return null on error to allow graceful degradation
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.
- 8d ago First seen · 73 lines · 0 tokens per session scan A 56fa5c508f4c
unleash-api-integration 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 503 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
python
Python best practices and patterns for modern software development with Flask and SQLite.
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
env-validation-gate
Env validation gate — every app with ≥1 required env var validates its contract at boot via Zod; raw process.env is banned outside the env module. Full pattern in .claude/skills/t2000-env-gate/.