growth-plan

growth-plan is a skill for Claude Code from indranilbanerjee/digital-marketing-pro. It costs 34 tokens per session (2,661 once invoked), scanned A, original, MIT.

A client-facing growth strategy document that brings earlier marketing work into one plan. It includes forecasts under three scenarios, budget allocation, and a 30/60/90-day timeline, and exports the result as PDF and DOCX files.

In plain words
What is it for?
It is for presenting an executable growth strategy, comparing forecast scenarios, dividing budget between in-market and out-market work, and setting an implementation schedule.
Why use it?
It turns separate analyses and preparation documents into one plan that explains how a business could grow, what it may cost, and when work should happen. It depends on earlier engagement parts being completed.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Part of the digital-marketing-pro plugin — 164 skills, 5 commands, 24 agents shipped together

Good fit It is for presenting an executable growth strategy, comparing forecast scenarios, dividing budget between in-market and out-market work, and setting an implementation schedule.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/indranilbanerjee/digital-marketing-pro/growth-plan
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.

Any agent
npx skills add indranilbanerjee/digital-marketing-pro --skill growth-plan
Clone the repo
git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro

Made for: Claude Code.

Or install digital-marketing-pro, the plugin that ships this one along with the rest of its 164 skills, 5 commands, 24 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-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/growth-plan/github.svg)](https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/growth-plan)
Your own site
<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/growth-plan"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/growth-plan/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-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/growth-plan"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/growth-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,661 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.00034 $0.02661
Opus 5.5 $0.00014 $0.01064
Sonnet 5.5 $0.00007 $0.00532
Haiku 4.5 $0.00003 $0.00266

Measured 18d ago against content hash db001c1d4a77, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

growth-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 18d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/growth-plan/SKILL.md · 240 lines

How it starts

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

/digital-marketing-pro:growth-plan — Part 8 Flagship Deliverable

The Growth Plan is the flagship client-facing deliverable. It synthesises every internal document produced in Parts 1–7 into a single 11-section narrative answering: "How will we grow this business digitally, and what will it cost?"

Context efficiency

Heavy skill. Grep before Read any referenced file, then Read only matched ranges with offset + limit. List the brand's data dir (~/.claude-marketing/brands/{slug}/, or $CLAUDE_PLUGIN_DATA/digital-marketing-pro/brands/{slug}/ when that env var is set) before opening files. On re-invocation mid-session, skip files already in context.

Specification: growth-plan-template.md — the canonical 11-section structure.

Pre-conditions

Before producing the Growth Plan, verify:

  1. Parts 1–7 completed in the engagement
  2. Four Core Documents at canonical version (v2 if re-runs happened, v1 otherwise)
  3. Living Project Instruction File current — reflects the current strategic facts
  4. Part 7 Preparation Documents completed — campaign architecture, naming conventions, KPI tree, content pillars, asset inventory, approval chains

If any pre-condition fails, do NOT produce. Instruct the user.

The 11 Sections

# Section Length Source
1 Executive Summary 1 page Synthesis
2 Business Context 2-3 pages Core Doc 3.1 + Part 4.4 + Part 4.2
3 Target Audience 2-3 pages Core Doc 3.2
4 Strategic Positioning 2 pages Core Doc 3.3
5 Channel Strategy 3-4 pages Core Doc 3.4 + Part 9 channel docs
6 Budget & Media Plan 2-3 pages Core Doc 3.4 Step 5 + 9
7 KPI Framework 2 pages Part 7 KPI tree
8 Implementation Timeline 2-3 pages Part 7 + 30/60/90 framework
9 Team & Resource Plan 1-2 pages Engagement context
10 Risk & Contingency 1-2 pages Core Doc 3.1 Step 16
11 Expected Outcomes 2 pages Three-scenario forecasting

Read the full file on GitHub · 240 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. 18d ago Changed · -127 tokens per session db001c1d4a77
  2. 23d ago Changed · -7 lines ca8647e5cc5f
  3. 1mo ago First seen · 247 lines · 161 tokens per session scan A 9546a30d19f5

Subscribe to this mod's changes

growth-plan is a skill published in the GitHub repository indranilbanerjee/digital-marketing-pro (912 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 2,661 once invoked, about $0.0001 per session on Opus 5.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-09-07.