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/gtmagents/gtm-agentsWrote 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/gtmagents/gtm-agents/generate-blog)<a href="https://agentmods.dev/commands/gtmagents/gtm-agents/generate-blog"><img src="https://agentmods.dev/badge/commands/gtmagents/gtm-agents/generate-blog/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/gtmagents/gtm-agents/generate-blog"><img src="https://agentmods.dev/badge/commands/gtmagents/gtm-agents/generate-blog.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.00017 | $0.00330 |
| Opus 5 | $0.00009 | $0.00165 |
| Sonnet 5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
generate-blog 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 8d 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
Generate Blog Command
Purpose
Create long-form blog content that balances SEO intent, persona pain points, and GTM storytelling.
Syntax
/content-marketing:generate-blog \
--topic "<working title>" \
--persona "<target role>" \
--keyword "<primary keyword>" \
--length 1200 \
--tone "authoritative"
Parameters
--topic: Core subject or angle for the post.--persona: Reader profile (CMO, Demand Gen Lead, Founder).--keyword: Primary keyword to optimize for.--length: Target word count (default 1200).--tone: voice (authoritative, conversational, visionary).--cta: Desired call-to-action (demo, download, subscribe).
Output Package
- SEO brief (H1/H2 structure, keyword usage, meta data).
- Draft article in Markdown with intro → body → CTA.
- Pull quotes, tweet thread, LinkedIn caption suggestions.
- Repurposing ideas (podcast segment, newsletter blurb, short video script).
Best Practices
- Map subheadings to buyer journey stages.
- Include statistics or quotes every ~300 words for credibility.
- Add internal/external links (3 each minimum).
- End with CTA tied to campaign objective.
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.
- 8d ago First seen · 43 lines · 17 tokens per session scan A 1f0f7a549348
generate-blog is a command published in the GitHub repository gtmagents/gtm-agents (398 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 330 once invoked, about $0.0001 per session on Opus 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-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.