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/hansonli05/cursor-rules-system/api-integration-examplegit clone --depth 1 https://github.com/Hansonli05/Cursor-rules-systemWhat 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.00007 | $0.02275 |
| Opus 5 | $0.00003 | $0.01137 |
| Sonnet 5 | $0.00001 | $0.00455 |
| Haiku 4.5 | $0.00001 | $0.00228 |
Grade A, and why
api-integration-example scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await fetch(url, config); How it starts
The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Integration (Example)
Summary
Defines consistent patterns for integrating with external APIs including error handling, retry logic, caching, and data transformation. This is an example template.
Context
API integrations are critical points of failure and complexity. Consistent patterns ensure reliability, maintainability, and good user experience even when external services have issues.
Instructions
API Client Structure
- Base Client: Common configuration, headers, interceptors
- Service Clients: Specific API endpoints and methods
- Error Handling: Consistent error types and recovery
- Retry Logic: Exponential backoff for transient failures
- Caching: Appropriate caching strategies per endpoint
Request/Response Flow
-
Request Preparation
- Validate input parameters
- Add authentication headers
- Apply request transformations
- Log request details (non-sensitive)
-
Request Execution
- Execute with timeout
- Handle network errors
- Implement retry logic
- Monitor request performance
-
Response Processing
- Validate response structure
- Transform data format
- Cache when appropriate
- Log response details
Examples
Base API Client
class BaseApiClient {
private baseURL: string;
private defaultTimeout: number = 10000;
constructor(baseURL: string) {
this.baseURL = baseURL;
}
async request<T>(
endpoint: string,
options: RequestOptions = {}
): Promise<ApiResponse<T>> {
const config = {
method: options.method || 'GET',
headers: {
'Content-Type': 'application/json',
...this.getAuthHeaders(),
...options.headers
},
timeout: options.timeout || this.defaultTimeout,
body: options.body ? JSON.stringify(options.body) : undefined
};
try {
const response = await this.executeWithRetry(
`${this.baseURL}${endpoint}`,
config,
options.retryOptions
);
return this.processResponse<T>(response);
} catch (error) {
throw this.handleError(error, endpoint);
}
}
private async executeWithRetry(
url: string,
config: RequestConfig,
retryOptions?: RetryOptions
): Promise<Response> {
const maxRetries = retryOptions?.maxRetries || 3;
const backoffMs = retryOptions?.backoffMs || 1000;
for (let attempt = 0; attempt <= maxRetries; attempt++) {
try {
const response = await fetch(url, config);
if (response.ok || !this.isRetryableError(response.status)) {
return response;
}
if (attempt === maxRetries) {
throw new ApiError('Max retries exceeded', response.status);
}
await this.delay(backoffMs * Math.pow(2, attempt));
} catch (error) {
if (attempt === maxRetries || !this.isRetryableError(error)) {
throw error;
}
await this.delay(backoffMs * Math.pow(2, attempt));
}
}
}
}
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.
- yesterday First seen · 372 lines · 7 tokens per session scan A cca9225887df
api-integration-example is a cursor rule published in the GitHub repository Hansonli05/Cursor-rules-system (2 stars, last pushed 1y ago), licensed MIT. It adds 7 tokens to every session and 2,275 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.