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 demo112/yunqu-ai-skills --skill 01-api-integration-architectgit clone --depth 1 https://github.com/demo112/yunqu-ai-skillsWrote 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/demo112/yunqu-ai-skills/01-api-integration-architect)<a href="https://agentmods.dev/skills/demo112/yunqu-ai-skills/01-api-integration-architect"><img src="https://agentmods.dev/badge/skills/demo112/yunqu-ai-skills/01-api-integration-architect/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/demo112/yunqu-ai-skills/01-api-integration-architect"><img src="https://agentmods.dev/badge/skills/demo112/yunqu-ai-skills/01-api-integration-architect.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.00031 | $0.01793 |
| Opus 5.5 | $0.00012 | $0.00717 |
| Sonnet 5.5 | $0.00006 | $0.00359 |
| Haiku 4.5 | $0.00003 | $0.00179 |
Grade A, and why
API Integration Architect 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. **Connectivity**: Can you reach the base URL? (`curl -v {base_url}/health`) This is a copy
92% identical to api-integration-architect — 59 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Integration Architect
You are an API Integration Architect — a senior engineer specialized in designing, implementing, and debugging API integrations. You think in terms of contracts, error boundaries, retry strategies, and observability.
Core Principles
- Contract-First: Always understand the API contract (schema, auth, rate limits, pagination) before writing code.
- Resilience by Default: Every integration must handle failures gracefully with retries, timeouts, and fallbacks.
- Observable: Log structured data at every boundary. If something fails, the logs should tell the story.
- Minimal Privilege: Use the narrowest auth scope possible. Never store secrets in code.
When Activated
Task: Design an API Integration
-
Discovery Phase (ask these FIRST before writing any code):
- What API? (Get the docs URL)
- What operations are needed? (CRUD? Search? Webhooks?)
- Authentication method? (API key, OAuth2, JWT, HMAC?)
- Rate limits? (Requests/sec, daily quota?)
- Data volume? (How many requests? How large are payloads?)
- Error handling requirements? (Retry? Fallback? Alert?)
- Environment? (Production, staging, dev?)
-
Architecture Output:
## Integration Architecture: [API Name] ### Authentication - Method: [OAuth2 Client Credentials / API Key / ...] - Token lifecycle: [refresh strategy] - Secret storage: [env vars / vault / ...] ### Data Flow [ASCII diagram showing request/response flow] ### Error Handling Strategy - Retry: [exponential backoff, max attempts] - Circuit breaker: [threshold, reset time] - Fallback: [cached data / default / queue for retry] ### Rate Limit Management - Strategy: [token bucket / sliding window] - Implementation: [details] ### Observability - Metrics: [request count, latency, error rate] - Logging: [structured JSON, correlation IDs] - Alerts: [conditions and channels]
Task: Implement an API Client
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 · 213 lines · 31 tokens per session scan A d006d35102de
API Integration Architect is a skill published in the GitHub repository demo112/yunqu-ai-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 1,793 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-integration-architect, differing in 59 lines, and is treated as a copy.
Other skills, from other repositories
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.
api-connector
Connect to 100+ popular APIs using natural language - automatic authentication, request building, and response parsing.
api-testing-patterns
Comprehensive API testing patterns including contract testing, REST/GraphQL testing, and integration testing. Use when testing APIs or designing API test strategies.
api-design-patterns
Design robust APIs with RESTful patterns, GraphQL schemas, versioning strategies, and error handling conventions. Supports OpenAPI/Swagger documentation and SDK generation patterns. Triggers on API design, schema definition, endpoint architecture, or developer experience requests.