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/craft-microsaas-narrative.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/craft-microsaas-narrative)<a href="https://agentmods.dev/commands/hollandkevint/thinkhaven/craft-microsaas-narrative"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/craft-microsaas-narrative/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/hollandkevint/thinkhaven/craft-microsaas-narrative"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/craft-microsaas-narrative.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.01813 |
| Opus 5 | $0.00000 | $0.00907 |
| Sonnet 5 | $0.00000 | $0.00363 |
| Haiku 4.5 | $0.00000 | $0.00181 |
Grade A, and why
craft-microsaas-narrative 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 6d 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 — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/craft-microsaas-narrative Task
When this command is used, execute the following task:
Craft MicroSaaS Narrative
Task Overview
Create compelling narratives around Kevin's solopreneur journey and MicroSaaS development that build audience, validate ideas, and drive business outcomes.
Prerequisites
- Current stage of MicroSaaS journey identified
- Target audience defined (customers, supporters, peers)
- Comfort level with transparency established
- Business goals for narrative clarified
Steps
1. Journey Stage Assessment
ELICIT: true Format: structured
I need to understand where Kevin is in the journey:
- Current Stage: Pre-launch, developing, launched, scaling?
- Product Status: Idea, prototype, MVP, full product?
- Business Metrics: Revenue stage, customer count, growth rate?
- Time Investment: Full-time, part-time, side project?
- Narrative Goals: What should this story accomplish?
2. Authenticity Boundaries Setting
ELICIT: true Format: comfort-levels
Let's establish what Kevin is comfortable sharing:
Financial Transparency:
- Revenue numbers: Exact, ranges, or general progress?
- Expenses: Development costs, tool spending?
- Personal finances: Impact of going solo?
Struggle Sharing:
- Technical challenges: Implementation difficulties?
- Business challenges: Customer acquisition, product-market fit?
- Personal challenges: Stress, uncertainty, family impact?
Success Celebration:
- Wins and milestones: Customer feedback, revenue growth?
- Learning achievements: Skills developed, insights gained?
- Recognition: Media mentions, community support?
3. Story Arc Development
I'll create a compelling narrative structure:
Origin Story Elements:
- Why Kevin chose solopreneurship
- The specific problem he couldn't stop thinking about
- The moment he decided to build a solution
- What he left behind and why
Journey Progression:
- Early struggles and learning curve
- Key milestones and breakthrough moments
- Setbacks and how they were overcome
- Evolution of the product and approach
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.
- 6d ago First seen · 336 lines · 0 tokens per session scan A f5ea43419ae1
craft-microsaas-narrative is a command published in the GitHub repository hollandkevint/thinkhaven (5 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,813 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.
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.