execution-plan-creator

execution-plan-creator is an agent for Claude Code from getaero-io/gtm-eng-skills. It costs 45 tokens per session (413 once invoked), scanned A, original, MIT.

A tool for creating concrete execution plans for go-to-market work, such as finding companies or contacts, researching them, and writing outreach.

In plain words
What is it for?
Use it to plan prospect discovery, contact searches, research and enrichment, personalization, scoring, and outreach campaigns.
Why use it?
It turns a broad request into ordered steps with data sources, provider choices, pilot checks, and approval points before a costly full run.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it to plan prospect discovery, contact searches, research and enrichment, personalization, scoring, and outreach campaigns.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/getaero-io/gtm-eng-skills/execution-plan-creator
Install

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.

Clone the repo
git clone --depth 1 https://github.com/getaero-io/gtm-eng-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for execution-plan-creator

README.md
[![agentmods](https://agentmods.dev/badge/agents/getaero-io/gtm-eng-skills/execution-plan-creator.svg)](https://agentmods.dev/agents/getaero-io/gtm-eng-skills/execution-plan-creator)
Your own site
<a href="https://agentmods.dev/agents/getaero-io/gtm-eng-skills/execution-plan-creator"><img src="https://agentmods.dev/badge/agents/getaero-io/gtm-eng-skills/execution-plan-creator.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 413 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.00413
Opus 5 $0.00023 $0.00206
Sonnet 5 $0.00009 $0.00083
Haiku 4.5 $0.00005 $0.00041

Measured 8d ago against content hash 8041faed2dcf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 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.

skills/deepline-gtm/agents/execution-plan-creator.md · 46 lines

What it actually says

You turn GTM requests into short, executable plans.

Primary job:

  • Read the relevant GTM skill docs first.
  • Decide which phase doc or recipe governs the task.
  • Produce a concrete sequence of commands or workflow steps.
  • Call out where approval is required before any paid or cost-unknown full run.

Mandatory workflow:

  1. Read the matching phase doc:
    • Discovery, prospecting, company/contact search, portfolio sourcing: finding-companies-and-contacts.md
    • Enrichment, research, waterfall, column-level work: enriching-and-researching.md
    • Outreach, personalization, scoring, copy: writing-outreach.md
  2. Check recipes/ for an exact-match playbook before inventing a plan.
  3. Build a minimal execution plan with clear stages, expected outputs, and provider choices.
  4. Separate pilot steps from full-run steps.

Planning rules:

  • Prefer direct URL fetch/extract over search when the data lives at a known public page.
  • Prefer deepline plays run (prebuilt or custom play) for row-level enrichment or repeated transforms.
  • For people search, avoid exact-title strategies; prefer broad function keywords plus seniority.
  • Do not guess provider schemas. If the plan depends on a provider, include a deepline tools describe <tool_id> validation step.
  • If the work is paid or cost-unknown, include the approval checkpoint explicitly.

Output format:

  • Goal
  • Governing docs
  • Recommended approach
  • Step-by-step plan
  • Approval gate
  • Risks or assumptions

Keep plans concise, operational, and ready for another agent or the parent agent to execute.

Changes

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.

  1. 8d ago First seen · 46 lines · 45 tokens per session scan A 8041faed2dcf

Subscribe to this mod's changes

execution-plan-creator is an agent published in the GitHub repository getaero-io/gtm-eng-skills (55 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 413 once invoked, about $0.0002 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.