Borrowing it
Nothing to install: this file belongs to hollandkevint/thinkhaven. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hollandkevint/thinkhaven/main/.claude/commands/kevinCreate/tasks/create-blog-article.mdgit clone --depth 1 https://github.com/hollandkevint/thinkhavenWrote 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/hollandkevint/thinkhaven/create-blog-article)<a href="https://agentmods.dev/commands/hollandkevint/thinkhaven/create-blog-article"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/create-blog-article.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.01589 |
| Opus 5 | $0.00000 | $0.00794 |
| Sonnet 5 | $0.00000 | $0.00318 |
| Haiku 4.5 | $0.00000 | $0.00159 |
Grade A, and why
create-blog-article 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 4d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/create-blog-article Task
When this command is used, execute the following task:
Create Blog Article
Task Overview
Transform a well-developed idea into a comprehensive, engaging blog article that establishes Kevin's expertise.
Prerequisites
- Content idea fully developed and validated
- Supporting evidence and examples identified
- Target audience clearly defined
- Blog structure template reviewed
Steps
1. Article Planning & Structure
ELICIT: true Format: structured
I need to understand the scope and structure:
- Core Topic: What's the main subject/argument?
- Target Length: 1,200-2,500 words typical - what feels right for this topic?
- Audience Level: Technical depth - beginner, intermediate, or expert?
- Primary Goal: Educate, persuade, establish authority, or drive action?
- Key Examples: What specific stories/cases will you include?
2. Opening Development
I'll craft a compelling hook using Kevin's proven patterns:
Opening Options:
- Personal Story: "Three years ago, I was sitting in a meeting room..."
- Surprising Fact: "70% of healthcare data initiatives fail, but not for the reasons you think..."
- Contrarian Take: "Everyone talks about data-driven decisions. But most data doesn't drive anything..."
- Problem Scenario: "Picture this: It's 2 AM, and your clinical team..."
ELICIT: true Format: choice
Which opening approach fits this topic best?
- [Personal story option]
- [Surprising fact option]
- [Contrarian take option]
- [Problem scenario option]
3. Problem Definition Section
I'll establish why this matters right now:
Structure:
- Current Industry State: What's happening in healthcare data/products
- Specific Pain Points: Real problems Kevin's audience faces
- Cost of Inaction: What happens if this isn't addressed
- Timing Context: Why this matters now specifically
Evidence Integration:
- Kevin's direct observations
- Industry statistics/trends
- Real customer/user feedback
- Competitive landscape insights
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.
- 4d ago First seen · 270 lines · 0 tokens per session scan A d1663f0a19c2
create-blog-article is a command published in the GitHub repository hollandkevint/thinkhaven (5 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,589 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-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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.