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/straddle-plannpx skills add straddleio/ai --skill straddle-plangit clone --depth 1 https://github.com/straddleio/aiWrote 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/straddleio/ai/straddle-plan)<a href="https://agentmods.dev/skills/straddleio/ai/straddle-plan"><img src="https://agentmods.dev/badge/skills/straddleio/ai/straddle-plan.svg" alt="Measured on agentmods" 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 | $0.00069 | $0.02257 |
| Opus 5 | $0.00034 | $0.01128 |
| Sonnet 5 | $0.00014 | $0.00451 |
| Haiku 4.5 | $0.00007 | $0.00226 |
Grade A, and why
straddle-plan 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 3d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Run a guided conversation (5-8 questions) that produces a complete Straddle integration plan. The plan covers entity mapping, API flows, code examples, webhook handlers, and compliance notes -- all tailored to the developer's specific use case and SDK language.
The plan is the artifact the developer uses to build their sandbox integration.
Scope boundaries
- Execute API calls -> use
sandbox-test - Answer ad-hoc integration questions -> use
straddle-integrate - Set up MCP/CLI/keys -> use
setup - Explain statuses -> use
explain-status
Point users to the appropriate skill if they ask for something outside scope.
Reference files
Read before generating each plan section. Shared with straddle-integrate:
| Topic | Reference |
|---|---|
| Entities, statuses, webhooks, ACH | <../straddle-integrate/references/domain.md> |
| Embed: onboarding, accounts, headers | <../straddle-integrate/references/embed.md> |
| Pay by Bank: customer, bridge, payments | <../straddle-integrate/references/pay-by-bank.md> |
| SDKs, Bridge Widget, errors | <../straddle-integrate/references/sdk.md> |
Doc search enforcement
Reference files contain stable structural and behavioral knowledge. Enumerated factual lists (return codes, event names, numeric limits) have been replaced with links to authoritative documentation pages.
Doc search tools:
search_docsMCP tool -- SDK and API reference (method signatures, parameters, code examples). Always passlanguageparam.- Product docs -- search by POSTing to
https://docs.straddle.com/mcpwith{"jsonrpc":"2.0","method":"tools/call","params":{"name":"search_straddle_docs","arguments":{"query":"YOUR_QUERY"}},"id":1}and headerAccept: application/json, text/event-stream. Returns payment guides, compliance, sandbox testing.
Default to search_docs for any code or API question.
For EACH section of the output plan:
- Read the relevant reference file for structural baseline
- Follow all documentation links in the reference file for current values
- Use
search_docs(passlanguageparam) for method signatures and code examples - Search product docs (POST to
https://docs.straddle.com/mcp) for current guides and compliance info - Compare all sources. MCP results win on conflicts (they are live). Flag discrepancies.
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.
- 3d ago First seen · 238 lines · 69 tokens per session scan A 604fc620caee
straddle-plan is a skill published in the GitHub repository straddleio/ai (5 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 2,257 once invoked, about $0.0003 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
convex-add
Add a capability to the CURRENT Convex app — consults the served Convex capability catalog for always-current procedures (billing, crons, auth, agent, search, …); falls back to built-in hosting or @convex-dev component search. TRIGGER when the user runs /add, or asks to add hosting/publishing or any backend capability…
twitter-reader
Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…
chenhao-limit-up
Use when evaluating A-share limit-up (涨停板) setups through Chen Hao's sentiment and momentum lens: market emotion cycles, board strength, follow-through, and short-term aggressive momentum trading.
trading-risk-gate
Unified pre-trade safety gate: Ruin check (Law #1), ergodicity audit, and win-rate dominance validation. Absorbs: ergodicity-check, law-of-ruin, win-rate-dominance.
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
multi-expert-analyzer
针对通用问题进行多领域专家联合分析, 综合稿产生前必经 fact-checker 与 red-team 两道独立校验。适用场景: 用户提出跨领域或不确定领域的复杂问题, 需要从多个专家角度分别搜证并相互校验后综合成文, 例如该不该买房、该不该跳槽、是否进入某个赛道等。触发关键词: 多角度分析、专家分析、综合分析、多视角、跨领域分析、从不同角度看、深度分析。问题只属于单一明确领域时, 优先使用该领域的专门 skill, 例如纯财务用 finance-core-analysis、纯技术用 software-architect。输出 (全部 markdown 保存到当前项目 markdown/ 目录): (1) 每位专家的中间分析稿…