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-integrationgit 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-integration)<a href="https://agentmods.dev/skills/lingxling/awesome-skills-cn/api-integration"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/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/skills/lingxling/awesome-skills-cn/api-integration"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/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.00027 | $0.01316 |
| Opus 5.5 | $0.00011 | $0.00526 |
| Sonnet 5.5 | $0.00005 | $0.00263 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
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 19d 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.
This is a copy
98% identical to api-integration — 28 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Integration Skill
When to Use
Use this skill when you need designs event-driven architectures, webhook systems, API chaining flows, ETL pipelines, and integration patterns between services. Use whenever the user asks about webhooks, event streaming, API composition, connecting two or more APIs, building pipelines, Pub/Sub, Kafka topics, ETL...
Design integration patterns, webhook flows, event pipelines, and API composition strategies.
Webhook Design
Outbound Webhook Endpoint (from your system to 3rd party)
POST {subscriber_url}
Headers:
Content-Type: application/json
X-Webhook-Signature: hmac-sha256=<sig>
X-Webhook-Event: order.created
X-Webhook-Delivery: <uuid>
X-Webhook-Timestamp: <unix-epoch>
Payload envelope
{
"event": "order.created",
"delivery_id": "uuid",
"created_at": "ISO8601",
"data": { ... }
}
Signature verification (receiver side):
import hmac, hashlib
expected = hmac.new(secret.encode(), payload_bytes, hashlib.sha256).hexdigest()
assert f"sha256={expected}" == request.headers["X-Webhook-Signature"]
Inbound Webhook Registration API
POST /api/v1/webhooks — register subscriber URL + events
GET /api/v1/webhooks — list subscriptions
DELETE /api/v1/webhooks/{id} — unsubscribe
POST /api/v1/webhooks/{id}/test — fire test event
GET /api/v1/webhooks/{id}/deliveries — delivery history + status
API Chaining / Composition Pattern
Step 1: POST /auth/token → get access_token
Step 2: GET /api/v1/user/profile → get user.id (use token from step 1)
Step 3: POST /api/v1/orders → create order (use user.id from step 2)
Step 4: POST /api/v1/payments → charge (use order.id from step 3)
Always: handle failures at each step independently, use idempotency keys, implement retry with exponential backoff.
Event-Driven Architecture
Event Schema (CloudEvents spec)
{
"specversion": "1.0",
"type": "com.example.order.created",
"source": "/orders-service",
"id": "uuid",
"time": "2024-01-01T00:00:00Z",
"datacontenttype": "application/json",
"data": { "order_id": "...", "amount": 99.99 }
}
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.
- 19d ago First seen · 176 lines · 27 tokens per session scan A 6e50f28c1866
api-integration is a skill published in the GitHub repository lingxling/awesome-skills-cn (321 stars, last pushed 19d ago), licensed MIT. It adds 27 tokens to every session and 1,316 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to api-integration, differing in 28 lines, and is treated as a copy.
Other skills, from other repositories
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…
nodejs-development
Node.js development guidelines covering Payload CMS, Vue.js with TypeScript, and general TypeScript best practices.
dotnet
Guidelines for .NET backend development with C#, ASP.NET Core, and Entity Framework Core.
microservices
Guidelines for building production-grade microservices with FastAPI/Python and Go, covering serverless patterns, clean architecture, observability, and resilience.
fullstack-expert
Expert-level fullstack development guide covering multi-language (TypeScript, Python, Go, Rust), API design (OpenAPI 3.1, gRPC), microservices, system design patterns, and polyglot architecture / Panduan fullstack tingkat ahli mencakup multi-bahasa, desain API, microservices, dan arsitektur polyglot.