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/straddleio/ai/product-docsnpx skills add straddleio/ai --skill product-docsgit clone --depth 1 https://github.com/straddleio/aiWhat 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.00077 | $0.00456 |
| Opus 5 | $0.00039 | $0.00228 |
| Sonnet 5 | $0.00015 | $0.00091 |
| Haiku 4.5 | $0.00008 | $0.00046 |
Grade A, and why
product-docs 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 2d 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.
curl -s -X POST https://docs.straddle.com/mcp \ What it actually says
What this searches
Straddle product documentation at docs.straddle.com: payment guides, sandbox testing, compliance rules, identity verification, webhook configuration, ACH return handling, and integration patterns.
For SDK and API reference (method signatures, parameters, response
shapes, code examples), use the search_docs MCP tool instead. That
tool is registered automatically and does not need this skill.
How to search
POST to the docs endpoint directly. No MCP registration or auth required.
curl -s -X POST https://docs.straddle.com/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"search_straddle_docs","arguments":{"query":"YOUR_QUERY"}},"id":1}'
Parse the SSE response: each result in the content array has text containing Title, Link, and Content fields as HTML-formatted strings.
When to use this vs search_docs
| Need | Tool |
|---|---|
| Method signatures, parameters, code examples | search_docs MCP tool (API reference) |
| Payment guides, compliance, sandbox testing | This skill (product docs) |
| How to call an endpoint | search_docs |
| How a feature works conceptually | This skill |
| Request/response shapes | search_docs |
| Status lifecycle, ACH returns, risk scores | This skill |
Documentation index
https://docs.straddle.com/llms.txt -- complete sitemap of all Straddle documentation pages with descriptions. Use as a fallback when the search does not return the needed content.
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.
- 2d ago First seen · 51 lines · 77 tokens per session scan A b4b3635f421e
product-docs is a skill published in the GitHub repository straddleio/ai (5 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 456 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…