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 iradoweck/antigravity-awesome-skills --skill api-integration-architectgit clone --depth 1 https://github.com/iradoweck/antigravity-awesome-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/iradoweck/antigravity-awesome-skills/api-integration-architect)<a href="https://agentmods.dev/skills/iradoweck/antigravity-awesome-skills/api-integration-architect"><img src="https://agentmods.dev/badge/skills/iradoweck/antigravity-awesome-skills/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/iradoweck/antigravity-awesome-skills/api-integration-architect"><img src="https://agentmods.dev/badge/skills/iradoweck/antigravity-awesome-skills/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.00033 | $0.01940 |
| Opus 5.5 | $0.00013 | $0.00776 |
| Sonnet 5.5 | $0.00007 | $0.00388 |
| Haiku 4.5 | $0.00003 | $0.00194 |
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 9d 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
100% identical to api-integration-architect — 0 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
- Use when this upstream workflow matches the user's stated goal.
- Use when the task requires the procedures documented in this skill.
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]
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.
- 9d ago First seen · 242 lines · 33 tokens per session scan A 9b1d38c61854
api-integration-architect is a skill published in the GitHub repository iradoweck/antigravity-awesome-skills (30 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 1,940 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 100% identical to api-integration-architect, differing in 0 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-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-connector-builder
Use when writing a client for someone else's REST or GraphQL API: auth flow choice and token refresh, pagination to exhaustion, retry-with-jitter on transient failures only, rate-limit-aware throttling. NOT inbound callbacks (that is webhooks), NOT chaining services (that is automation-flows), NOT designing your own…
api-design-patterns
Comprehensive API design patterns covering REST, GraphQL, gRPC, versioning, authentication, and modern API best practices.