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 skills/misonl/ling/api-patternsnpx skills add MisonL/Ling --skill api-patternsgit clone --depth 1 https://github.com/MisonL/LingWhat 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.00048 | $0.01028 |
| Opus 5 | $0.00024 | $0.00514 |
| Sonnet 5 | $0.00010 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
api-patterns 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 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.
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Patterns（API 模式）
API design principles and decision-making for 2025（2025 年 API 设计原则与决策逻辑）。 Learn to THINK, not copy fixed patterns（学习如何思考，而非机械复制固定模式）。
选择性阅读规则（Selective Reading Rule）
仅阅读与当前请求相关的文件（Read ONLY files relevant to the request）！ 查阅内容地图并定位所需章节（Check the content map, find what you need）。
内容地图（Content Map）
| File（文件） | Description（描述） | When to Read（阅读时机） |
|---|---|---|
api-style.md |
REST vs GraphQL vs tRPC decision tree（决策树） | Choosing API type（选择 API 类型时） |
rest.md |
Resource naming, HTTP methods, status codes（资源命名/HTTP 方法/状态码） | Designing REST API（设计 REST API 时） |
response.md |
Envelope pattern, error format, pagination（信封模式/错误格式/分页） | Response structure（确定响应结构时） |
graphql.md |
Schema design, when to use, security（模式设计/使用场景/安全性） | Considering GraphQL（考虑 GraphQL 时） |
trpc.md |
TypeScript monorepo, type safety（TS 单仓/类型安全） | TS fullstack projects（TS 全栈项目） |
versioning.md |
URI/Header/Query versioning（URI/请求头/查询参数版本控制） | API evolution planning（规划 API 演进） |
auth.md |
JWT, OAuth, Passkey, API Keys（认证方案） | Auth pattern selection（选择认证模式） |
rate-limiting.md |
Token bucket, sliding window（令牌桶/滑动窗口） | API protection（API 保护机制） |
documentation.md |
OpenAPI/Swagger best practices（文档规范） | Documentation（编写 API 文档） |
security-testing.md |
OWASP API Top 10, auth/authz testing（认证/授权测试） | Security audits（安全审计） |
相关技能（Related Skills）
| Need（需求） | Skill（技能） |
|---|---|
| API implementation（API 落地实现） | @[skills/nodejs-best-practices] |
| Data structure（数据库结构设计） | @[skills/database-design] |
| Security details（安全加固细节） | @[skills/vulnerability-scanner] |
[OK] 决策检查清单（Decision Checklist）
设计 API 之前（Before designing an API）：
- Asked user about API consumers?（是否询问 API 消费者？）
- Chosen API style for THIS context?（是否为当前上下文选择 API 风格？） (REST/GraphQL/tRPC)
- Defined consistent response format?（是否定义统一响应格式？）
- Planned versioning strategy?（是否规划版本控制策略？）
- Considered authentication needs?（是否考虑认证需求？）
- Planned rate limiting?（是否规划频率限制？）
- Documentation approach defined?（是否定义文档方案？）
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 85 lines · 48 tokens per session scan A c40bb652d84c
api-patterns is a skill published in the GitHub repository MisonL/Ling (9 stars, last pushed 5mo ago), licensed MIT. It adds 48 tokens to every session and 1,028 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…