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/develop-content-idea.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/develop-content-idea)<a href="https://agentmods.dev/commands/hollandkevint/thinkhaven/develop-content-idea"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/develop-content-idea.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.00868 |
| Opus 5 | $0.00000 | $0.00434 |
| Sonnet 5 | $0.00000 | $0.00174 |
| Haiku 4.5 | $0.00000 | $0.00087 |
Grade A, and why
develop-content-idea 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 3d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/develop-content-idea Task
When this command is used, execute the following task:
Develop Content Idea
Task Overview
Transform a raw concept into a well-developed content idea ready for creation.
Prerequisites
- Basic topic or concept identified
- Understanding of Kevin's expertise areas
- Access to thought development checklist
Steps
1. Idea Capture & Context
ELICIT: true Format: structured
I need to understand your initial concept. Please provide:
- Raw Idea: What's the basic concept? (e.g., "data quality is overrated")
- Origin: Where did this idea come from? (personal experience, observation, frustration)
- Initial Angle: What's your gut feeling about the unique perspective?
- Target Audience: Who needs to hear this? (data PMs, healthcare leaders, solopreneurs)
2. Expertise Validation
I'll assess whether this aligns with Kevin's credibility:
- Domain Fit: Does this leverage Kevin's healthcare/data expertise?
- Experience Base: Can Kevin speak from actual implementation?
- Authenticity Check: Would Kevin naturally discuss this topic?
- Authority Level: Is Kevin qualified to lead this conversation?
3. Uniqueness Assessment
ELICIT: true Format: choice
Let me challenge the uniqueness of this idea:
Here are the potential unique angles I see:
- [Contrarian take on conventional wisdom]
- [Personal experience-based insight]
- [Technical implementation reality]
- [Healthcare-specific application]
- [Solopreneur perspective]
Which resonates most, or do you see a different angle?
4. Evidence Gathering
I'll help identify supporting material:
- Personal Stories: Kevin's relevant experiences
- Industry Examples: Real companies/situations
- Data Points: Statistics or metrics if available
- Contrarian Evidence: Why conventional wisdom fails
- Implementation Reality: What actually happens in practice
5. Value Proposition Development
ELICIT: true Format: structured
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.
- 3d ago First seen · 142 lines · 0 tokens per session scan A ee788ff22ff8
develop-content-idea 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 868 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.