Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/adidacta/pmf-detective/update-value-propgit clone --depth 1 https://github.com/adidacta/pmf-detectiveWrote 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/adidacta/pmf-detective/update-value-prop)<a href="https://agentmods.dev/commands/adidacta/pmf-detective/update-value-prop"><img src="https://agentmods.dev/badge/commands/adidacta/pmf-detective/update-value-prop.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 | $0.00005 | $0.00715 |
| Opus 5 | $0.00003 | $0.00358 |
| Sonnet 5 | $0.00001 | $0.00143 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
update-value-prop 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 5d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Value Prop
Update the Value Proposition section of your PMF context layer.
Instructions
-
Check if
pmf/value-prop.mdexists- If exists: Read it and show summary, ask what to update
- If not: Inform user and offer to create it
-
If file exists, show current state:
┌───────────────────────────────────────────────────────────────┐
│ CURRENT VALUE PROPOSITION │
├───────────────────────────────────────────────────────────────┤
│ │
│ Callout: [3-part descriptor] │
│ Magnet: [Desired future] │
│ Message: [Selected value prop] │
│ CTA: [Call to action] → validation goal │
│ │
│ Alternatives: [N] saved for A/B testing │
│ │
└───────────────────────────────────────────────────────────────┘
- Use AskUserQuestion: "What would you like to update about your value proposition?"
Options:
-
"The Callout" — description: "Refine what makes your ICP stop and say 'that's me'"
-
"The Magnet" — description: "Refine the desired future / promised outcome"
-
"The Message" — description: "Regenerate value prop options from current Callout + Magnet"
-
"CTA" — description: "Update the call to action (your validation goal)"
-
"Switch to an alternative" — description: "Promote a different angle to primary"
-
"Start over completely" — description: "Rebuild from scratch using value-prop-builder"
-
Handle each option:
Option 1: The Callout
- Show current Callout (Identity, Context, Pain/Fear)
- Run Phase B from value-prop-builder (generate new Callout options from ICP data)
- After new Callout is set, regenerate value prop options (Phase D) and let user re-pick
Option 2: The Magnet
- Show current Magnet
- Run Phase C from value-prop-builder (generate new Magnet options from ICP data)
- After new Magnet is set, regenerate value prop options (Phase D) and let user re-pick
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.
- 5d ago First seen · 82 lines · 5 tokens per session scan A 0bf29d5e8ee9
update-value-prop is a command published in the GitHub repository adidacta/pmf-detective (18 stars, last pushed 6mo ago), licensed MIT. It adds 5 tokens to every session and 715 once invoked, about $0.0000 per session on Opus 5. 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-30.
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.