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 cwinvestments/memstack --skill api-integrationgit clone --depth 1 https://github.com/cwinvestments/memstackWrote 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/cwinvestments/memstack/api-integration)<a href="https://agentmods.dev/skills/cwinvestments/memstack/api-integration"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/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/cwinvestments/memstack/api-integration"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/api-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00098 | $0.02735 |
| Opus 5.5 | $0.00039 | $0.01094 |
| Sonnet 5.5 | $0.00020 | $0.00547 |
| Haiku 4.5 | $0.00010 | $0.00274 |
Grade A, and why
memstack-automation-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 2mo 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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Integration: Building system connector...
Develops system-to-system connectors with REST/GraphQL patterns, authentication flows, rate limit handling, data mapping, error recovery, and SDK wrapper generation.
Activation
When this skill activates, output:
API Integration: Building system connector...
Then execute the protocol below.
Context Guard
| Context | Status |
|---|---|
| User says "API integration", "connect APIs", "sync data" | ACTIVE |
| User says "data mapping" or "rate limiting" | ACTIVE |
| User needs to build a connector between two systems | ACTIVE |
| User wants a visual n8n workflow | DORMANT: use n8n Workflow Builder |
| User wants to receive webhooks | DORMANT: use Webhook Designer |
Common Mistakes
| Mistake | Why It's Wrong |
|---|---|
| "Ignore rate limits" | Getting blocked by the API wastes hours of debugging. Implement rate limiting from day one. |
| "No retry logic" | APIs have transient failures. Without retry + backoff, your sync silently drops data. |
| "Store tokens in code" | Use environment variables or a secrets manager. Tokens in code end up in git history. |
| "Map fields manually every time" | Build a reusable mapping layer. Manual field-by-field transforms are fragile and hard to update. |
| "No pagination handling" | Most APIs return paginated results. If you only read page 1, you're missing data. |
Protocol
Step 1: Gather Integration Requirements
If the user hasn't provided details, ask:
- Source system: where does the data come from? (API name, docs URL)
- Destination: where does it go? (your DB, another API, file)
- Data: what entities are synced? (users, orders, products, events)
- Direction: one-way, two-way, or event-driven?
- Auth: how does the API authenticate? (API key, OAuth 2.0, JWT, Basic)
- Volume: how much data? How often? (1K records/day vs 1M)
Step 2: Implement Authentication
| Auth Type | Implementation | Token Lifecycle |
|---|---|---|
| API Key | Header: X-API-Key: {key} or query param |
Static: rotate manually |
| Bearer Token | Header: Authorization: Bearer {token} |
Expires: refresh needed |
| OAuth 2.0 | Auth code flow → access + refresh tokens | Auto-refresh on 401 |
| JWT | Sign claims → Authorization: Bearer {jwt} |
Short-lived: re-sign |
| Basic Auth | Header: Authorization: Basic {base64} |
Static |
| HMAC | Sign request body → custom header | Per-request signing |
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.
- 2mo ago Changed db1d5b2c29e2
- 2mo ago First seen · 344 lines · 98 tokens per session scan A 2cd925a14dd8
memstack-automation-api-integration is a skill published in the GitHub repository cwinvestments/memstack (429 stars, last pushed 13d ago), licensed MIT. It adds 98 tokens to every session and 2,735 once invoked, about $0.0004 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-30.
memstack-automation-api-integration compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| memstack-automation-api-integrationcwinvestments/memstack | Skill | 429 | 13d ago | MIT | A | 98 | Claude Code |
| agent-django-fastapi-experttravisjneuman/.claude | Skill | 107 | yesterday | MIT | A | 92 | Claude Code |
| microservices-architecturetravisjneuman/.claude | Skill | 107 | yesterday | MIT | A | 30 | Claude Code, Codex |
| netlify-developmentMindrally/skills | Skill | 297 | 29d ago | Apache-2.0 | A | 78 | Claude Code |
| authentication-patternstravisjneuman/.claude | Skill | 107 | yesterday | MIT | A | 28 | Claude Code, Codex |
| email-systemstravisjneuman/.claude | Skill | 107 | yesterday | MIT | A | 55 | Claude Code, Codex |
| event-driven-architecturetravisjneuman/.claude | Skill | 107 | yesterday | MIT | A | 50 | Claude Code, Codex |