unleash-api-integration

unleash-api-integration is a cursor rule for Cursor from cuongtl1992/unleash-mcp. It costs 0 tokens per session (503 once invoked), scanned A, original, MIT.

Coding rules for adding integrations with the Unleash API, a service for managing feature toggles that turn software features on or off.

In plain words
What is it for?
Use them when implementing functions that call Unleash endpoints and return API data or a null result when a request fails.
Why use it?
They provide consistent file locations, naming, request handling, error handling, and documentation for new integrations.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use them when implementing functions that call Unleash endpoints and return API data or a null result when a request fails.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/cuongtl1992/unleash-mcp/unleash-api-integration
Install

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.

Clone the repo
git clone --depth 1 https://github.com/cuongtl1992/unleash-mcp

Made for: Cursor.

Wrote 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.

agentmods badge for unleash-api-integration

README.md
[![agentmods](https://agentmods.dev/badge/rules/cuongtl1992/unleash-mcp/unleash-api-integration.svg)](https://agentmods.dev/rules/cuongtl1992/unleash-mcp/unleash-api-integration)
Your own site
<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>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 503 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 56fa5c508f4c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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.

.cursor/rules/unleash-api-integration.mdc · 73 lines

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

  1. Import the Unleash client:
import { client } from "./unleash-client.js";
  1. 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;
  }
}
  1. 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
 */
  1. 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
  2. For POST/PUT requests, follow this pattern:

const response = await client.post('/api/admin/endpoint', {
  property1: value1,
  property2: value2
});
  1. Use proper TypeScript types:
    • Define interfaces for request/response data
    • Use specific return types rather than any when 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

Read the full file on GitHub · 73 lines

Changes

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.

  1. 8d ago First seen · 73 lines · 0 tokens per session scan A 56fa5c508f4c

Subscribe to this mod's changes

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.