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 agents/getcargohq/cargo-skills/execution-plan-creatorgit clone --depth 1 https://github.com/getcargohq/cargo-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/agents/getcargohq/cargo-skills/execution-plan-creator)<a href="https://agentmods.dev/agents/getcargohq/cargo-skills/execution-plan-creator"><img src="https://agentmods.dev/badge/agents/getcargohq/cargo-skills/execution-plan-creator.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.00000 | $0.01456 |
| Opus 5 | $0.00000 | $0.00728 |
| Sonnet 5 | $0.00000 | $0.00291 |
| Haiku 4.5 | $0.00000 | $0.00146 |
Grade A, and why
execution-plan-creator 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 today.
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent — Execution Plan Creator
Sub-agent for cargo-gtm. Takes a user goal and returns a step-by-step plan citing specific provider + action slugs with cost estimates.
When to invoke this agent
- The user's goal touches multiple stages (sourcing → enrichment → verification → sequencing) and the right path isn't obvious.
- The user asks "what would this cost?" or wants a budget estimate before executing.
- A recipe doesn't perfectly match — you need to compose a custom chain.
For goals matching an existing recipe in ../recipes/, use the recipe directly — don't invoke this agent.
What this agent produces
A structured plan with:
- Goal restatement — one sentence confirming intent.
- Assumptions defined operationally — every judgment call spelled out as a testable rule (not "best contact" but "highest-ranked current employee matching RevOps/GTM-ops titles, weighted Chief > VP > Head > Director > Lead > Manager"), plus data decisions already made and the cost trade-off chosen.
- Stage breakdown — each step labelled with stage (SOURCE / DEDUPE / ENRICH / SIGNAL / CONTACT / VERIFY / BACKFILL / WRITE-BACK / SEQUENCE / SYNC), with provider + action slug + cost per step — anchored in the priority stack where possible; long-tail providers only when priority can't serve the criteria.
- Sample step + budget reconciliation — the plan's first executed step is always a sample: 1–3 rows when the plan is a single action, 10–20 records when any step fans out as a batch (a 2-row sample can't produce a hit-rate, and hit-rate drives the estimate). The full-run estimate is grounded in the sample's observed per-row cost, states how many records the full run enrolls, and is reconciled against the actual balance (
billing subscription get). If the estimate exceeds the balance, the plan says so up front. - Approval question with 3 shaped choices — run-until-cap / top-up-then-run / trim-scope-to-fit (with a proposed trimming heuristic). Never bare yes/no.
- Open questions for the user — anything ambiguous (segment source, contact volume per company, write-back destination).
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.
- today Changed · +1 lines 3ad0c7989ec0
- 4d ago First seen · 95 lines · 0 tokens per session scan A 20f5f0c958b7
execution-plan-creator is an agent published in the GitHub repository getcargohq/cargo-skills (17 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,456 tokens. 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.
Other agents, from other repositories
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.
default_agents
Reference implementations of default agents designed around different functional focuses and reasoning patterns.
ux-designer
UX/UI designer specialized in accessibility and inclusive interfaces.
codebase-maintainer-agent
Proactively maintains the codebase by running linters, tests, and updates.
reviewer
Strong read-only reviewer / synthesizer (Opus 5). Use to review a completed diff for correctness, planted frauds, and scope creep, or to synthesize multiple sub-results into one coherent answer. Cites file:line. Returns a VERIFIED / VERIFIED WITH CAVEATS / REFUTED verdict. Never writes code.