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 agentmods add commands/agentii-ai/growth-hacking-kit/growthkit-specifygit clone --depth 1 https://github.com/agentii-ai/growth-hacking-kitWrote 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/commands/agentii-ai/growth-hacking-kit/growthkit-specify)<a href="https://agentmods.dev/commands/agentii-ai/growth-hacking-kit/growthkit-specify"><img src="https://agentmods.dev/badge/commands/agentii-ai/growth-hacking-kit/growthkit-specify.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.00000 | $0.00442 |
| Opus 5 | $0.00000 | $0.00221 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
growthkit-specify 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 6d 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
/growthkit.specify
Create a campaign specification for systematic growth hacking.
Usage
Run this command to generate a campaign specification from your campaign description.
Basic Example
/growthkit.specify Launch Product Hunt campaign with demo video, first-100-user incentives, and maker community engagement strategy
What This Does
This command will:
- Create a new feature branch with format
###-campaign-name(e.g.,001-product-hunt-launch) - Generate
specs/###-campaign-name/spec.mdwith:- User stories covering complete campaign workflow
- Functional requirements for all campaign aspects
- Success criteria with measurable outcomes
- Edge case handling
- Run Constitution Check validation to ensure:
- Growth type is identified (Vibe/Trust/Agentic)
- Target audience is specific (not generic)
- Viral loop mechanism is defined (Remix/Integration/Watermark)
- k-factor target is set (>1.1 for sustainable growth)
- Metrics are defined (primary, activation, engagement)
- Flag ambiguous requirements with [NEEDS CLARIFICATION] markers (max 3)
- Validate specification quality against checklists
Next Steps
Once your specification is validated:
- Read the generated
spec.mdto understand campaign requirements - Review Constitution Check results - ensure all mandatory gates pass
- Run
/growthkit.planto design platform-specific implementation tactics - Run
/growthkit.tasksto generate actionable task breakdown - Run
/growthkit.implementto execute campaign
Tips
- Be specific about target audience (e.g., "junior Python devs learning FastAPI" not just "developers")
- Define at least one viral loop (how users share/discover the campaign)
- Include success metrics (what does good look like?)
- Mention platforms you plan to use (X/Twitter, TikTok, LinkedIn, GitHub, Product Hunt)
- Explain why this campaign matters to your business
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.
- 6d ago First seen · 51 lines · 0 tokens per session scan A 0116b529793c
growthkit-specify is a command published in the GitHub repository agentii-ai/growth-hacking-kit (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 442 tokens. 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.
Other commands, from other repositories
content-engine
Draft blog posts, ad copy, emails, social media, landing pages, and video scripts with brand voice and SEO.
performance-report
Generate a marketing performance report with KPI tracking, trend analysis, anomaly detection, and recommendations.
seo-drift
Compare two SEO snapshots (GSC / GSC AI Performance / rank tracker / AEO probe) and surface top movers per metric with auto-classification — growth / decline / reshuffle / stable / new / lost.
community-harvest
Mine community channels (Discord, Slack, Telegram) for recurring questions, pain points, and feature requests. Produces actionable content briefs and documentation gap reports.
lesson-capture
Record structured lessons after significant tasks. Builds a persistent knowledge base that improves future agent performance. Run with an optional summary or use review to read past lessons.
security-audit
Full security scan of the workspace. Checks for credential leaks, file permissions, gitignore coverage, and hardcoded secrets.