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 skills add phuonghx/aim-cli --skill api-patternsgit clone --depth 1 https://github.com/phuonghx/aim-cliWrote 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/skills/phuonghx/aim-cli/api-patterns)<a href="https://agentmods.dev/skills/phuonghx/aim-cli/api-patterns"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/api-patterns/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/skills/phuonghx/aim-cli/api-patterns"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/api-patterns.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.00086 | $0.00724 |
| Opus 5.5 | $0.00034 | $0.00290 |
| Sonnet 5.5 | $0.00017 | $0.00145 |
| Haiku 4.5 | $0.00009 | $0.00072 |
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 1mo 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Patterns
Reason about API design from first principles. The goal is judgment for your situation, not a template to paste.
How to use this skill
These notes are split into focused files. Open only the one that maps to the question in front of you instead of reading everything at once. The table below is your index.
File index
| File | Covers | Open it when |
|---|---|---|
api-style.md |
Picking REST vs GraphQL vs tRPC | Deciding the paradigm |
rest.md |
Resource names, verbs, status codes | Laying out a REST surface |
response.md |
Payload shape, errors, paging | Shaping what you return |
graphql.md |
Schema modeling, fit, hardening | Weighing GraphQL |
trpc.md |
Typed TS client/server | Full-stack TypeScript work |
versioning.md |
URI / header / query schemes | Planning for change |
auth.md |
Tokens, sessions, OAuth, keys | Picking how callers prove identity |
rate-limiting.md |
Quotas and throttling | Shielding the service |
documentation.md |
OpenAPI and reference docs | Writing the docs |
security-testing.md |
OWASP API risks, authz checks | Reviewing for security |
Sibling skills
| If you also need | Reach for |
|---|---|
| To actually build the endpoints | @[skills/nodejs-best-practices] |
| To model the underlying data | @[skills/database-design] |
| A deeper security pass | @[skills/vulnerability-scanner] |
Pre-flight checklist
Run through these before committing to a design:
- Who calls this API, and from where? (asked, not assumed)
- Paradigm chosen for this problem (REST / GraphQL / tRPC)
- One response shape, applied everywhere
- A story for how the API changes over time
- Identity and access model decided
- Throttling thought through
- A plan for keeping docs alive
Traps to avoid
Stop doing this:
- Reaching for REST reflexively on every project
- Naming endpoints after actions (e.g.
/fetchUsers) - Letting each route return a differently shaped body
- Leaking stack traces or DB errors to callers
- Shipping with no throttling at all
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.
- 1mo ago First seen · 82 lines · 86 tokens per session scan A 645d8aab5a56
api-patterns is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 3mo ago), licensed MIT. It adds 86 tokens to every session and 724 once invoked, about $0.0003 per session on Opus 5.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
node-modern
Use this skill when writing, reviewing, or refactoring Node.js code — modules, async flow, cancellation, file and process I/O, HTTP — on a current Node.js release. Triggers: user mentions "Node", "Node.js", "ESM", "CommonJS", "require", "import", "fetch", "AbortSignal", "AbortController", "stream", "childprocess"…
api-design
Use this skill when designing, implementing, or reviewing an HTTP API — endpoints, request and response shapes, errors, pagination, versioning, and authorization. Triggers: user says "API", "endpoint", "REST", "route", "status code", "pagination", "request body", "response shape", "OpenAPI", "versioning"…
configure-server
Configures how the MCP Task Orchestrator SERVER runs and is reached — transport (HTTP vs STDIO), the REST API, port publishing, config mounts, and config-sync. Use when a user says: run the server, register the image, set up the Docker container, enable the REST API, set up config-sync, reconfigure the server, change…
nextjs-modern
Build, migrate, and debug Next.js 16 App Router applications with React 19, Server Components, Server Actions, explicit caching, and production deployment. Use when implementing Next.js routes, upgrading to the latest stable Next.js, or fixing rendering and cache behavior.
authentication-sessions
Implement application sign-in, sessions and identity integration with explicit account/tenant authorization. Use when building OAuth/OIDC, passkeys, password login or session renewal; use security-scanner for a requested defensive review.
cloudflare-workers
Build and maintain Cloudflare Workers with typed bindings, explicit compatibility and isolated validation. Use when implementing Workers handlers, integrating KV/R2/D1/Durable Objects/Queues or configuring Wrangler; deployment remains governed by the user task and target environment.