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/bmadPMF/tasks/design-manual-delivery.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/design-manual-delivery)<a href="https://agentmods.dev/commands/hollandkevint/thinkhaven/design-manual-delivery"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/design-manual-delivery/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/design-manual-delivery"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/design-manual-delivery.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.01354 |
| Opus 5 | $0.00000 | $0.00677 |
| Sonnet 5 | $0.00000 | $0.00271 |
| Haiku 4.5 | $0.00000 | $0.00135 |
Grade A, and why
design-manual-delivery 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 11d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design-manual-delivery Task
When this command is used, execute the following task:
Design Manual Delivery Task
Purpose
To create a manual delivery approach that ensures customer success and reveals the key drivers of retention. By doing things that don't scale first, you understand exactly what creates customer "equilibrium" before building automated systems.
Inputs
- Signed customer or strong verbal commitment
- Clear understanding of promised results
- Timeline expectations from sales process
- Resources available (your time, tools, team)
- Technical capabilities currently available
Key Activities & Instructions
1. Define Success Outcome
Document exactly what success looks like:
- Customer's Definition: In their words from sales call
- Measurable Outcome: Specific metrics or milestones
- Timeline: When they expect to see results
- Evidence of Success: How they'll know it worked
- <critical_rule>Success must be defined before delivery begins</critical_rule>
2. Map the Manual Journey
Design the customer journey from purchase to success:
2.1 Onboarding Phase (Days 1-7)
- Welcome sequence design
- Expectation setting communication
- Initial data/access gathering
- Quick win identification
- First value delivery target
2.2 Implementation Phase (Weeks 1-4)
- Weekly milestone mapping
- Manual work required from you
- Customer effort needed
- Checkpoint conversations
- Progress tracking method
2.3 Success Phase (Months 1-3)
- Success metric monitoring
- Usage pattern establishment
- Habit formation support
- Value reinforcement cadence
- Expansion opportunity identification
3. Identify Manual Components
List everything you'll do manually initially:
Data/Process Work:
- Data entry or transformation
- Report generation
- Analysis or insights creation
- Integration or connection work
- Quality checking
Communication Touch Points:
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.
- 11d ago First seen · 253 lines · 0 tokens per session scan A 3c11e89254c3
design-manual-delivery is a command published in the GitHub repository hollandkevint/thinkhaven (5 stars, last pushed 12d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,354 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-31.
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.