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/2154355737/JieShenSheQuWrote 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/2154355737/jieshenshequ/03-api-integration)<a href="https://agentmods.dev/rules/2154355737/jieshenshequ/03-api-integration"><img src="https://agentmods.dev/badge/rules/2154355737/jieshenshequ/03-api-integration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/2154355737/jieshenshequ/03-api-integration"><img src="https://agentmods.dev/badge/rules/2154355737/jieshenshequ/03-api-integration.svg" alt="Reviewed on agentmods" width="80" 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.02968 |
| Opus 5.5 | $0.00000 | $0.01187 |
| Sonnet 5.5 | $0.00000 | $0.00594 |
| Haiku 4.5 | $0.00000 | $0.00297 |
Grade A, and why
03-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 2mo 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 — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API集成规范
🌐 API客户端配置
1. 统一API客户端
// ✅ 推荐: 创建统一的API客户端
const API_BASE_URL = import.meta.env.VITE_API_URL || 'http://localhost:8080/api/v1';
export const apiClient = {
get: async <T>(url: string, config?: RequestInit): Promise<T> => {
const response = await fetch(`${API_BASE_URL}${url}`, {
...config,
method: 'GET',
headers: {
'Content-Type': 'application/json',
...getAuthHeaders(),
...config?.headers,
},
});
return handleResponse<T>(response);
},
post: async <T>(url: string, data?: unknown, config?: RequestInit): Promise<T> => {
const response = await fetch(`${API_BASE_URL}${url}`, {
...config,
method: 'POST',
headers: {
'Content-Type': 'application/json',
...getAuthHeaders(),
...config?.headers,
},
body: JSON.stringify(data),
});
return handleResponse<T>(response);
},
// PUT, DELETE等方法...
};
// 获取认证头
const getAuthHeaders = (): Record<string, string> => {
const token = localStorage.getItem('token');
return token ? { Authorization: `Bearer ${token}` } : {};
};
// 统一响应处理
const handleResponse = async <T>(response: Response): Promise<T> => {
if (!response.ok) {
const error = await response.json().catch(() => ({ message: 'Network error' }));
throw new ApiError(error.message, response.status);
}
const data = await response.json();
return data.data as T;
};
2. 自定义错误类
export class ApiError extends Error {
constructor(
message: string,
public status: number,
public code?: string
) {
super(message);
this.name = 'ApiError';
}
}
📦 API类型定义
1. 请求和响应类型
// 用户相关类型
export interface User {
id: string;
username: string;
email: string;
avatar?: string;
role: 'admin' | 'user' | 'guest';
created_at: string;
updated_at: string;
}
export interface LoginRequest {
username: string;
password: string;
}
export interface LoginResponse {
token: string;
refresh_token: string;
user: User;
}
// API响应包装类型
export interface ApiResponse<T> {
code: number;
message: string;
data?: T;
errors?: ValidationError[];
}
export interface PaginatedResponse<T> {
data: T[];
total: number;
page: number;
size: number;
}
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.
- 2mo ago First seen · 475 lines · 0 tokens per session scan A 35125c965247
03-api-integration is a cursor rule published in the GitHub repository 2154355737/JieShenSheQu (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,968 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
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
python
Python best practices and patterns for modern software development with Flask and SQLite.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
selectools-providers
Rules for working with LLM provider adapters in selectools.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.