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 lingxling/awesome-skills-cn --skill api-analyzergit clone --depth 1 https://github.com/lingxling/awesome-skills-cnWrote 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/lingxling/awesome-skills-cn/api-analyzer)<a href="https://agentmods.dev/skills/lingxling/awesome-skills-cn/api-analyzer"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/api-analyzer/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/lingxling/awesome-skills-cn/api-analyzer"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/api-analyzer.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.00030 | $0.01006 |
| Opus 5.5 | $0.00012 | $0.00402 |
| Sonnet 5.5 | $0.00006 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
api-analyzer 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Use this skill when you need validates whether an API request is correct based on provided inputs (method, URL, headers, body, auth, query params). Use this skill whenever a user wants to check, validate, debug, or verif This is a copy
92% identical to api-analyzer — 36 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Analyzer
When to Use
Use this skill when you need validates whether an API request is correct based on provided inputs (method, URL, headers, body, auth, query params). Use this skill whenever a user wants to check, validate, debug, or verify an API call — including when they paste a curl command, show endpoint details, ask "is this...
Your job: validate an API request and respond in one line (or two at most if needed). Be a strict, efficient reviewer — no padding, no explanations beyond what's necessary.
Output Rules
- ✅ If correct: one line —
Looks correct.orValid request. - ❌ If incorrect: one line — state the error + one-line fix. Example:
Missing Authorization header — add \Authorization: Bearer `.` - ⚠️ If ambiguous: ask one targeted question before validating. Never ask more than one question at a time. Only ask if the missing info would change your verdict.
When to Ask a Question
Ask only if the answer could flip your assessment. Examples:
- POST/PUT/PATCH with no body → ask:
Is there a request body? - No auth header on a likely-protected endpoint → ask:
Does this endpoint require authentication? - Ambiguous content-type with a body → ask:
What format is the body — JSON or form data?
Do not ask about things that don't affect correctness (e.g., optional headers, environment details).
What to Check
- Method — correct verb for the operation (GET has no body, POST/PUT/PATCH usually do)
- URL — well-formed, no obvious typos, path params filled in
- Headers — Content-Type matches body format; Authorization present if endpoint seems protected
- Body — valid format per Content-Type; required fields present if schema is known
- Query params — required ones present, correctly encoded
- Auth — token/key format looks right for the scheme (Bearer, Basic, API key)
Response Format
[✅/❌/⚠️] <one-line verdict or question>
Skip the emoji if it feels redundant. Never add preamble like "Sure!" or postamble like "Let me know if you need more help."
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.
- 10d ago First seen · 102 lines · 30 tokens per session scan A 5b06a4022c27
api-analyzer is a skill published in the GitHub repository lingxling/awesome-skills-cn (312 stars, last pushed 10d ago), licensed MIT. It adds 30 tokens to every session and 1,006 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 92% identical to api-analyzer, differing in 36 lines, and is treated as a copy.
Other skills, from other repositories
mm-doctor
A diagnostic workflow for checking the health of the mm system, including its configuration, project links, note vault, passports, session archive, and planning consistency.
holdfast
Warm, playful exploration of shared worlds, distributed systems, and questions that want a stranger frame. Follow an intriguing association beyond the usual protocol menu; make room for unfinished ideas without rushing to appraisal or an implementation plan. Not a distributed-correctness audit.
api-design
Design production-grade REST, GraphQL, gRPC, and Python library APIs with correct schemas, error contracts, auth, and versioning. Use when the user asks to design an API, define endpoints, create an OpenAPI/Swagger spec, design a GraphQL schema, build a gRPC service, model request/response with Pydantic, add…
content-modelling
Design CMS content models — content types, fields, editorial workflows, governance rules, and COPE (Create Once, Publish Everywhere) patterns — for structured, multi-channel publishing. Use when the user asks to design a content model, define content types in a CMS, structure fields for editorial content, plan a…
error-handling
Expert at building resilient applications through proper error handling. Covers Result types, error boundaries, try-catch patterns, typed errors, and graceful degradation. Use when "error handling, try catch, error boundary, Result type, exception, error-handling, typescript, react, resilience" mentioned.
concurrency-safety
A set of rules for writing safe concurrent and asynchronous code, where multiple tasks may run at the same time. It covers shared state, race conditions, deadlocks, timeouts, cancellation, and resource cleanup.