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 agentmods add skills/outboundsync/skills/apinpx skills add outboundsync/skills --skill apigit clone --depth 1 https://github.com/outboundsync/skillsWhat 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 | $0.00121 | $0.02305 |
| Opus 5 | $0.00060 | $0.01153 |
| Sonnet 5 | $0.00024 | $0.00461 |
| Haiku 4.5 | $0.00012 | $0.00231 |
Grade A, and why
api 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 yesterday.
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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OutboundSync API v1
Teach and lightly exercise the public API. Default read-only. Never print, log, or commit the API key. Never print webhook signing secrets. Treat sources[].url and destinations[].url as sensitive (full paste only when the user needs to copy them).
Render only the fixed output shape below — no prose outside it.
Note: These instructions reflect OutboundSync best practices shared freely and without warranty of outcomes — see DISCLAIMER.md.
Credentials
- Load
$OUTBOUNDSYNC_API_KEYfrom the environment (Bearer token). - Base:
https://app.outboundsync.com/api/v1 - Docs: https://outboundsync.com/docs/api/v1/
- Keys: https://outboundsync.com/docs/api/authentication/creating-api-keys/
Thin map: references/endpoints.md. Prior-outreach contract: references/contacts-outreach.md.
Auth and scopes
| Concern | Rule |
|---|---|
| Header | Authorization: Bearer osapi_… |
| Default scope | read (GETs) |
| Mutations | Require write on the key (POST/PATCH/DELETE, rotate, test, replay, blocklist pause/resync) — not this skill |
| Account-scoped key | Sees all connections; required for /webhooks* |
| Connection-scoped key | Sees one connection; fine for introspection + narrowed /events; 403 on /webhooks* |
| Rate limits | Honor 429 + Retry-After; GET /contacts/outreach has a dedicated 600/60s bucket |
On 401 / 403 / 429, summarize the error meaning and the shortest fix — do not invent admin flags beyond the response body.
Vocabulary (keep distinct)
| Concept | API term | Path / field |
|---|---|---|
| SEP inbound paste URL | source | GET /sources (url) |
| Forward raw events to customer HTTPS | destination (forwarding) | catalog GET /destinations; bindings still nested on GET /sources (sources[].destinations[]) |
| Reply-CC a sales rep | destination (reply relay) | GET /destinations/reply-relays (+ bound on sources) |
| Prior-outreach lookup | contacts/outreach | GET /contacts/outreach |
| CRM→SEP blocklist sync configs | blocklists | GET /blocklists — not contacts/outreach blocklists.* (reserved; evaluated always false) |
| OutboundSync-emitted Sync Monitoring | webhooks + events | /webhooks, /events |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 148 lines · 121 tokens per session scan A 900ce7d0597a
api is a skill published in the GitHub repository outboundsync/skills (2 stars, last pushed 4d ago), licensed MIT. It adds 121 tokens to every session and 2,305 once invoked, about $0.0006 per session on Opus 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…