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.
git 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/specify)<a href="https://agentmods.dev/commands/agentii-ai/growth-hacking-kit/specify"><img src="https://agentmods.dev/badge/commands/agentii-ai/growth-hacking-kit/specify/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/commands/agentii-ai/growth-hacking-kit/specify"><img src="https://agentmods.dev/badge/commands/agentii-ai/growth-hacking-kit/specify.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.00013 | $0.02793 |
| Opus 5.5 | $0.00005 | $0.01117 |
| Sonnet 5.5 | $0.00003 | $0.00559 |
| Haiku 4.5 | $0.00001 | $0.00279 |
Grade A, and why
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 1mo 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
73% identical to specify — 207 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
The text the user typed after /speckit.specify in the triggering message is the feature description. Assume you always have it available in this conversation even if {ARGS} appears literally below. Do not ask the user to repeat it unless they provided an empty command.
Given that feature description, do this:
-
Generate a concise short name (2-4 words) for the branch:
- Analyze the feature description and extract the most meaningful keywords
- Create a 2-4 word short name that captures the essence of the feature
- Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug")
- Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)
- Keep it concise but descriptive enough to understand the feature at a glance
- Examples:
- "I want to add user authentication" → "user-auth"
- "Implement OAuth2 integration for the API" → "oauth2-api-integration"
- "Create a dashboard for analytics" → "analytics-dashboard"
- "Fix payment processing timeout bug" → "fix-payment-timeout"
-
Check for existing branches before creating new one:
a. First, fetch all remote branches to ensure we have the latest information:
git fetch --all --pruneb. Find the highest feature number across all sources for the short-name:
- Remote branches:
git ls-remote --heads origin | grep -E 'refs/heads/[0-9]+-<short-name>$' - Local branches:
git branch | grep -E '^[* ]*[0-9]+-<short-name>$' - Specs directories: Check for directories matching
specs/[0-9]+-<short-name>
c. Determine the next available number:
- Extract all numbers from all three sources
- Find the highest number N
- Use N+1 for the new branch number
d. Run the script
{SCRIPT}with the calculated number and short-name:- Pass
--number N+1and--short-name "your-short-name"along with the feature description - Bash example:
{SCRIPT} --json --number 5 --short-name "user-auth" "Add user authentication" - PowerShell example:
{SCRIPT} -Json -Number 5 -ShortName "user-auth" "Add user authentication"
- Remote branches:
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.
- 1mo ago First seen · 261 lines · 13 tokens per session scan A 2e9a9c5e1314
specify is a command published in the GitHub repository agentii-ai/growth-hacking-kit (5 stars, last pushed 9mo ago), licensed MIT. It adds 13 tokens to every session and 2,793 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 73% identical to specify, differing in 207 lines, and is treated as a copy.
Other commands, from other repositories
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.
blog-draft
Write a 1,200-2,000 word blog article as plain semantic HTML from an approved outline. Second step in the blog production pipeline.
upgrade
Update EVC to the latest version, re-render templates with current config, and show what changed.
export-clean
Strip internal-only elements (version drawer, review notes) from a staging HTML file to produce a clean export ready for CMS upload or public sharing.
content-plan
Weekly content planning for {{COMPANYNAME}}'s Monday-Friday social content. The brain of the content engine.