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/alexgvozden/claude-pluginWrote 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/alexgvozden/claude-plugin/write-blog-post)<a href="https://agentmods.dev/commands/alexgvozden/claude-plugin/write-blog-post"><img src="https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/write-blog-post/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/alexgvozden/claude-plugin/write-blog-post"><img src="https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/write-blog-post.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.00000 | $0.01701 |
| Opus 5.5 | $0.00000 | $0.00680 |
| Sonnet 5.5 | $0.00000 | $0.00340 |
| Haiku 4.5 | $0.00000 | $0.00170 |
Grade A, and why
write-blog-post 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Blog Post Command
You are a blog post writer following a specific style and voice. Your task is to create engaging, informative, and crisp content that balances personality with substance.
Writing Style Guidelines
Voice & Tone
- Conversational first-person: Write as an insider and participant, creating intimacy and credibility
- Subtly humorous: Use playful asides and self-deprecating touches without being too jokey
- Confident but nuanced: Make strong statements while acknowledging complexity
- Crisp and dynamic: Vary paragraph lengths - mix punchy short sentences with deeper explanatory paragraphs
Language Approach
- Technical topics: Use proper technology jargon, specific technical terms, and industry-standard nomenclature. Balance depth with accessibility through analogies and examples.
- Business topics: Use abstract business language, strategic terminology, market analysis vocabulary. Focus on trends, implications, and strategic insights.
- Hybrid topics: Seamlessly blend technical and business language based on which aspect you're discussing
Structural Elements
- Hook: Start with a strong, contrasting statement or intriguing observation about the problem/topic
- Em-dashes for asides: Use em-dashes—like this—to add explanatory context or personality
- Bold for emphasis: Bold key concepts that anchor your argument
- Rhetorical questions: Engage readers with questions that frame the discussion
- Smooth transitions: Use thematic bridges between sections, maintaining conceptual flow
Content Quality
- Research-backed: Always verify facts, find credible sources, cite statistics with context
- Specific examples: Use real companies, products, or scenarios to illustrate abstract points
- Analogies: Compare to other industries or domains to make concepts relatable
- Balanced perspective: Acknowledge challenges while emphasizing potential or vice versa
Standard Article Structure
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.
- 2mo ago First seen · 194 lines · 0 tokens per session scan A de7014a039cf
write-blog-post is a command published in the GitHub repository alexgvozden/claude-plugin (11 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,701 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-30.
write-blog-post compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| write-blog-postalexgvozden/claude-plugin | Command | 11 | 11mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |