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/analyze-sales-call.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/analyze-sales-call)<a href="https://agentmods.dev/commands/hollandkevint/thinkhaven/analyze-sales-call"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/analyze-sales-call/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/analyze-sales-call"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/analyze-sales-call.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.01402 |
| Opus 5 | $0.00000 | $0.00701 |
| Sonnet 5 | $0.00000 | $0.00280 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
analyze-sales-call 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 10d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/analyze-sales-call Task
When this command is used, execute the following task:
Analyze Sales Call Task
Purpose
To systematically extract insights from sales conversations that reveal demand patterns, friction points, and opportunities for case study refinement. Every call is data that brings you closer to product-market fit.
Inputs
- Recording or detailed notes from recent sales call
- Current case study version used in the call
- Prospect information (role, company, context)
- Call outcome (next steps, objections, interest level)
- Your gut feeling about what went well/poorly
Key Activities & Instructions
1. Call Setup Documentation
Record the context for proper analysis:
- Prospect Profile: Role, company size, industry
- How They Found You: Inbound/outbound, referral source
- Pre-Call Research: What you knew going in
- Their Stated Interest: Why they took the meeting
- Case Study Version: Which variation you presented
2. Energy and Engagement Mapping
Track engagement throughout the call:
2.1 High Energy Moments
- When did they lean in or get excited?
- What specific words/phrases sparked interest?
- Which slides/sections generated questions?
- When did they start selling themselves?
2.2 Energy Drops
- Where did enthusiasm wane?
- Which sections felt like pushing uphill?
- When did they disengage or multitask?
- What triggered skepticism or doubt?
<critical_rule>Map energy shifts to specific case study sections</critical_rule>
3. Question Analysis
Document and interpret every question asked:
| Question Asked | Underlying Concern | What This Reveals |
|---|---|---|
| "How long does implementation take?" | Risk/effort concern | Need clearer "How" section |
| "Who else uses this?" | Social proof needed | Add customer examples |
| "Can it integrate with X?" | Technical feasibility | Address in options |
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.
- 10d ago First seen · 223 lines · 0 tokens per session scan A 841b92f40db5
analyze-sales-call 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,402 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.