agentmods.dev

growth-proposal

growth-proposal is a command for Claude Code from prashishh/seo-geo-report-engine. It costs 22 tokens per session (606 once invoked), scanned A, original, MIT.

A command for building a branded growth-proposal PDF from client information, research, and notes. The proposal presents a three-part plan covering foundations, acquisition, and conversion or retention.

In plain words
What is it for?
Use it to create, render, and review a client's proposal, including opportunity sizing and conservative, probable, and aggressive projections.
Why use it?
It gathers the required evidence and turns it into a structured proposal with explicit assumptions and growth scenarios.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./bin/mkt proposal build --project $1.

Part of the seo-geo-report-engine plugin — 33 skills, 8 commands, 5 agents shipped together

not rated 5repo 2mo ago A scan 22 tokens original MIT

Good fit Use it to create, render, and review a client's proposal, including opportunity sizing and conservative, probable, and aggressive projections.

Compare 6 commands from other repositories ↓
View source ↗ prashishh/seo-geo-report-engine aeoseo-visibility.prashish.xyz
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/prashishh/seo-geo-report-engine
agentmods
npx agentmods add commands/prashishh/seo-geo-report-engine/growth-proposal

Made for: Claude Code.

Or install seo-geo-report-engine, the plugin that ships this one along with the rest of its 33 skills, 8 commands, 5 agents.

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 growth-proposal

README.md
[![agentmods](https://agentmods.dev/badge/commands/prashishh/seo-geo-report-engine/growth-proposal/github.svg)](https://agentmods.dev/commands/prashishh/seo-geo-report-engine/growth-proposal)
Your own site
<a href="https://agentmods.dev/commands/prashishh/seo-geo-report-engine/growth-proposal"><img src="https://agentmods.dev/badge/commands/prashishh/seo-geo-report-engine/growth-proposal/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for growth-proposal

Your own site · 80×15
<a href="https://agentmods.dev/commands/prashishh/seo-geo-report-engine/growth-proposal"><img src="https://agentmods.dev/badge/commands/prashishh/seo-geo-report-engine/growth-proposal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 606 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.00022 $0.00606
Opus 5 $0.00011 $0.00303
Sonnet 5 $0.00004 $0.00121
Haiku 4.5 $0.00002 $0.00061

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

Security

Grade A, and why

growth-proposal 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 12d 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.

commands/growth-proposal.md · 47 lines

How it starts

The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/growth-proposal

Thin workflow that produces the growth-proposal PDF (the 3-pillar deck) for $1 (defaults to the active project — resolve with ./bin/mkt config show). The methodology and all the real work live in the proposal-builder skill and playbooks/proposal-methodology.md; this command just gathers the inputs, invokes the skill, renders, and reviews.

Steps

  1. Gather inputs. ./bin/mkt config show --project $1. Read client.yml (profile, ICP, competitors, target keywords, brand colors, market) and everything in projects/$1/research/ — especially DISCOVERY.md if /discovery-audit has run. Glob the brief/notes in projects/$1/inputs/. If research/ is empty, suggest running /discovery-audit $1 first (the proposal is stronger with evidence), or let the skill fill the minimal gaps itself.

  2. Invoke proposal-builder. Hand it the project. The skill: resolves context, fills only the research gaps the deck needs (Ahrefs MCP first), picks the spine (Foundation → Wide Net/ Acquisition → Conversion/Lifecycle), sizes the opportunity, builds conservative/probable/ aggressive scenarios from explicit assumptions, and composes projects/$1/proposal.yml per templates/proposal/proposal.schema.md.

  3. Render the PDF.

    ./bin/mkt proposal build --project $1

    → writes projects/$1/deliverables/$1-growth-proposal.{html,pdf}.

  4. Review the PDF. Open / Read the rendered pages. Check: cover, the three pillar cards, chart readability, page breaks, no escaped-quote artifacts, and that numbers are consistent across sections (the scenario table matches the chart matches the scorecards). Iterate on proposal.yml and rebuild until clean.

  5. Report back. Summarize the headline KPIs, the scenario assumptions, and any open questions the user should confirm before this goes to the client.

Notes

  • Every projection must be falsifiable — tied to an assumption the reader can challenge. Label illustrative/assumed numbers as such; never imply data we didn't pull.
  • Brand comes from client.yml: brand (primary + accent); falls back to config/framework.yml.
  • Keep it tight — the reference decks are ~10 pages, one strong chart per section.

Read the full file on GitHub · 47 lines

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. 12d ago First seen · 47 lines · 22 tokens per session scan A f20d7d510f28

Subscribe to this mod's changes

growth-proposal is a command published in the GitHub repository prashishh/seo-geo-report-engine (5 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 606 once invoked, about $0.0001 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.

DocumentsMarketing and SEOPDFgeomarketingmarketing-agentsseo
Related

Other commands, from other repositories

visibly-seo-pdf-build

Build a brand-compliant PDF from a Python script.

AntonioBlago/claude-code-seo-starter · 10 tokens

seo-geo

SEO/GEO end-to-end along the SITE loop: survey demand and competitors, implement content, tune quality/tech/on-page, and evaluate authority/rankings/reports/memory (--phase survey|implement|tune|evaluate). Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 58 tokens

email

Run an email-marketing (SEND) workflow: deliverability/consent setup, segmentation, email creative, lifecycle flows, newsletter monetization, send-testing, and the email-quality audit gate. Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 50 tokens

launch

Run a product-launch (RAMP) workflow: positioning and launch tiering, window/early-access design, message house and asset kits, the launch-readiness gate with a T-1 go/no-go, launch-day execution, and the post-launch prove loop. Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 64 tokens

narrative

Run a brand-narrative & messaging (TALE) workflow: trace the current message and positioning truth, architect the durable message house/voice/story canon, land it consistently across every surface, and evaluate resonance with tests and drift monitoring. Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 59 tokens

social

Run an organic-social (ECHO) workflow: channel portfolio and voice dossiers, platform-native content and calendars, the social-quality gate with a pre-publish go/no-go, community/inbox/crisis operations, and the listening/SOV/dark-social measurement loop. Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 64 tokens