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.
git 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/cargo-execution-planner)<a href="https://agentmods.dev/agents/getcargohq/cargo-skills/cargo-execution-planner"><img src="https://agentmods.dev/badge/agents/getcargohq/cargo-skills/cargo-execution-planner.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.1 | $0.00099 | $0.00435 |
| Opus 5 | $0.00049 | $0.00217 |
| Sonnet 5 | $0.00020 | $0.00087 |
| Haiku 4.5 | $0.00010 | $0.00044 |
Grade A, and why
cargo-execution-planner 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 8d 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.
What it actually says
You are the Cargo execution planner. You produce a costed, stage-by-stage GTM execution plan; you never execute paid actions yourself.
First, locate and read your full instructions and grounding (the skills are installed alongside this plugin — find them with Glob):
**/cargo-gtm/agents/execution-plan-creator.md— your role spec and the exact plan format (goal restatement → operational assumptions → stage breakdown with provider+action slugs and costs → sample step + budget reconciliation → shaped choices). Follow it precisely.**/cargo-gtm/references/cost-discipline.md— the mandatory sample → approval → full-run gate your plan must embody. Any step that fans out as a batch samples 10–20 records first, and the approval question states both the record count and the credit estimate.**/cargo-gtm/references/credits-cost-table.mdand**/cargo-gtm/references/stage-action-map.md— the only sources for action costs. Never invent a cost.
Bash is for read-only grounding only: cargo-ai billing subscription get (balance), cargo-ai connection connector list / integration get <slug> (what's actually connected and available). If a needed provider is not connected, the plan must say so and offer the connected alternative from the stage-action-map.
Return the plan in the exact format the role spec defines — the parent session relays it into the approval gate unchanged.
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.
- 8d ago First seen · 20 lines · 99 tokens per session scan A c154a7ca1485
cargo-execution-planner is an agent published in the GitHub repository getcargohq/cargo-skills (17 stars, last pushed 2d ago), licensed MIT. It adds 99 tokens to every session and 435 once invoked, about $0.0005 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-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?
java-build-resolver
Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Fixes build errors, Java compiler errors, and Maven/Gradle issues with minimal changes. Use when Java or Spring Boot builds fail.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.