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/blogkit.checklist)<a href="https://agentmods.dev/commands/agentii-ai/growth-hacking-kit/blogkit.checklist"><img src="https://agentmods.dev/badge/commands/agentii-ai/growth-hacking-kit/blogkit.checklist/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/blogkit.checklist"><img src="https://agentmods.dev/badge/commands/agentii-ai/growth-hacking-kit/blogkit.checklist.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.00012 | $0.01490 |
| Opus 5.5 | $0.00005 | $0.00596 |
| Sonnet 5.5 | $0.00002 | $0.00298 |
| Haiku 4.5 | $0.00001 | $0.00149 |
Grade A, and why
blogkit.checklist 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
100% identical to blogkit.checklist — 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 — 146 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
Generate custom quality checklists based on blog type and content requirements:
-
Load spec.md and plan.md:
- Identify blog type (Authority, Practitioner, Community, Thought Leadership)
- Extract target audience, content pillars, success criteria
- Identify content focuses (technical, non-technical, mix)
-
Generate Blog-Type Specific Checklists:
Authority Blog Checklist (deep research, citations):
- Competitive analysis completed (5-10 competitor posts reviewed)
- Unique angle identified (not just summarizing existing content)
- Research methodology documented (sources, data, interviews)
- Original data/research included (benchmarks, surveys, case studies)
- Backlink strategy defined (which sites might link here?)
- Internal content cluster documented (which posts link to/from this?)
- External expert citations included (quotes, links, references)
- SEO potential verified (target keyword < 5K monthly searches)
Practitioner Blog Checklist (practical how-tos, tutorials):
- Prerequisites clearly stated upfront
- Step-by-step instructions verified in clean environment
- Code examples tested and working end-to-end
- Expected output shown for each code example
- Troubleshooting section included (common issues & fixes)
- Time estimate provided (how long to complete?)
- Dependencies documented (what needs to be installed?)
- Next steps provided (what to learn after completing this?)
Community Blog Checklist (spotlights, case studies):
- Subject/contributor given advance notice and approval
- Story told in subject's own words (when possible)
- Highlights subject's unique contributions to community
- Links to subject's work, social, projects included
- Call-to-action for community to follow subject
- Published on subject's social channels (cross-promotion)
- Community members encouraged to comment/engage
- Follow-up plan (how will we stay connected?)
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 · 146 lines · 12 tokens per session scan A fee5f172cad4
blogkit.checklist is a command published in the GitHub repository agentii-ai/growth-hacking-kit (5 stars, last pushed 9mo ago), licensed MIT. It adds 12 tokens to every session and 1,490 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to blogkit.checklist, differing in 0 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.