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/dokkabei97/forged-claude-code/value-propositiongit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/value-proposition)<a href="https://agentmods.dev/commands/dokkabei97/forged-claude-code/value-proposition"><img src="https://agentmods.dev/badge/commands/dokkabei97/forged-claude-code/value-proposition.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.00024 | $0.01476 |
| Opus 5 | $0.00012 | $0.00738 |
| Sonnet 5 | $0.00005 | $0.00295 |
| Haiku 4.5 | $0.00002 | $0.00148 |
Grade A, and why
value-proposition 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/value-proposition - Value Proposition Generator
Triggers
- When defining or refining product messaging
- When pivoting and need to re-articulate value
- When preparing pitch deck, landing page, or marketing copy
- When answering "why should anyone use this?"
Usage
/value-proposition [product description]
/value-proposition "AI-powered code review tool for small teams"
/value-proposition --canvas # Full Value Proposition Canvas
/value-proposition --oneliner # Just the one-liner
/value-proposition --compare [competitor] # Differentiated positioning
Behavioral Flow
Phase 1: Understand the Product
Gather or infer from context:
- What is it? (1 sentence)
- Who is it for? (specific target user)
- What problem does it solve? (pain point)
- How does it solve it differently? (differentiation)
- What's the key benefit? (outcome, not feature)
Phase 2: Jobs-to-be-Done Analysis
## Customer Jobs
### Functional Jobs (what they're trying to do)
- [Job 1]: [description]
- [Job 2]: [description]
### Emotional Jobs (how they want to feel)
- [Job]: [e.g., Feel confident in code quality]
### Social Jobs (how they want to be perceived)
- [Job]: [e.g., Be seen as a modern engineering team]
## Pains (현재 겪는 고통)
| Pain | Severity (1-5) | Current Workaround |
|------|----------------|-------------------|
| [Pain 1] | [N] | [How they cope today] |
| [Pain 2] | [N] | [How they cope today] |
## Gains (원하는 결과)
| Gain | Importance (1-5) | How Product Delivers |
|------|-------------------|---------------------|
| [Gain 1] | [N] | [Product capability] |
| [Gain 2] | [N] | [Product capability] |
Phase 3: Generate Value Propositions
Formula Templates:
- Classic Format:
For [target customer] who [statement of need/opportunity], [product name] is a [product category] that [key benefit]. Unlike [competitor/alternative], our product [primary differentiator].
- Before/After/Bridge:
Before: [Customer's current painful situation] After: [Customer's desired improved situation] Bridge: [How your product gets them there]
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 · 196 lines · 24 tokens per session scan A b4092b86fb23
value-proposition is a command published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 24 tokens to every session and 1,476 once invoked, about $0.0001 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-31.
Other commands, from other repositories
lesson-capture
Record structured lessons after significant tasks. Builds a persistent knowledge base that improves future agent performance. Run with an optional summary or use review to read past lessons.
export-clean
Strip internal-only elements (version drawer, review notes) from a staging HTML file to produce a clean export ready for CMS upload or public sharing.
redbeacon-diagnose
诊断 — 「这期文案/图不行」时，反推问题出在定位/选题/文案预设/图片哪个节点，再对话调准.
intel-scan
Weekly intelligence gathering for the {{COMPANYNAME}} content engine. Run on Sunday evening or Monday morning before content planning.
growth-plan
Turn diagnosis into a sized greenfield opportunity map + a sequenced, mechanism-driven capture plan to overtake competitors.
content-status
Scan all content directories and report status of drafts, ideas, and published content.