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/write-linkedin-post.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/write-linkedin-post)<a href="https://agentmods.dev/commands/hollandkevint/thinkhaven/write-linkedin-post"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/write-linkedin-post.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.00784 |
| Opus 5 | $0.00000 | $0.00392 |
| Sonnet 5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
write-linkedin-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 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/write-linkedin-post Task
When this command is used, execute the following task:
Write LinkedIn Post
Task Overview
Transform an idea into a high-engagement LinkedIn post following Kevin's proven format and voice.
Prerequisites
- Clear topic or insight to share
- Understanding of target audience (data PMs, healthcare tech, B2B SaaS)
- Access to Kevin's writing principles
Steps
1. Idea Validation
ELICIT: true Format: structured
I need to understand your post idea. Please provide:
- Core Topic: What's the main idea? (e.g., "Why data PMs fail at stakeholder management")
- Key Insight: What's the surprising or valuable takeaway?
- Target Audience: Who specifically needs to hear this?
- Personal Angle: What's Kevin's unique experience with this?
2. Hook Development
Based on your input, I'll create hook variations (might be 2, might be 6 - not always 3-5):
- Contrarian take ("Everyone's wrong about X")
- Surprising statistic ("73% of data products fail")
- Personal vulnerability ("I screwed this up for 3 years")
- Pattern recognition ("After seeing this 10 times...")
- Direct challenge ("You're probably doing X wrong")
- Specific moment ("Last Tuesday at 3pm I realized...")
- Dialogue opener ("My CEO said 'Just ship it'")
ELICIT: true Format: choice
Here are your hook options: [I'll present 3-5 options]
Which resonates most? (Enter number or suggest edit)
3. Structure Creation
I'll build the post structure (but mix it up):
Option A - Classic
- Hook + Re-hook
- 2-7 insights (vary it!)
- Personal story
- CTA
Option B - Story-First
- Personal anecdote
- What I learned
- Here's the framework
- Try it yourself
Option C - Data-Driven
- Shocking stat
- Why it matters
- What I did about it
- Your move
Option D - Contrarian
- Challenge belief
- Evidence against it
- My experience
- What do you think?
4. Content Development
I'll write the full post following:
- Short paragraphs (2-3 lines max)
- Active voice only
- Concrete examples
- Kevin's conversational tone
- Platform optimization
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 · 144 lines · 0 tokens per session scan A d0975b1af0f5
write-linkedin-post 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 784 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.