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 skills add indranilbanerjee/neels-plugins --skill growth-plangit clone --depth 1 https://github.com/indranilbanerjee/neels-pluginsWrote 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/skills/indranilbanerjee/neels-plugins/growth-plan)<a href="https://agentmods.dev/skills/indranilbanerjee/neels-plugins/growth-plan"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/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.
<a href="https://agentmods.dev/skills/indranilbanerjee/neels-plugins/growth-plan"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/growth-plan.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.02661 |
| Opus 5.5 | $0.00014 | $0.01064 |
| Sonnet 5.5 | $0.00007 | $0.00532 |
| Haiku 4.5 | $0.00003 | $0.00266 |
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 2d 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.
This is a copy
94% identical to growth-plan — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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:
- Parts 1–7 completed in the engagement
- Four Core Documents at canonical version (v2 if re-runs happened, v1 otherwise)
- Living Project Instruction File current — reflects the current strategic facts
- 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 |
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.
- 2d ago First seen · 240 lines · 34 tokens per session scan A db001c1d4a77
growth-plan is a skill published in the GitHub repository indranilbanerjee/neels-plugins (6 stars, last pushed 2d ago), 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. It is 94% identical to growth-plan, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
continuous-improvement-loop
Run the Part 12 continuous improvement loop into a quarterly brief for leadership. "produce the quarterly improvement brief".
yearly-planner
Produce the Part 8 yearly planner: quarterly themes and monthly initiatives. "plan the whole year month by month".
attribution-report
Run attribution on real conversion paths, comparing models. "which channels actually drive revenue".
validate-output
Validate content structure against a schema: sections, word counts. "scan for leftover placeholders".
add-integration
Add a custom MCP integration: scaffold the server, write .mcp.json, test it. "add a new MCP server".
client-proposal
Draft a client proposal or RFP response: scope, deliverables, KPIs, pricing tiers. "respond to this RFP".