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 skills add daddia/claude-for-strategy --skill benefits-mapgit clone --depth 1 https://github.com/daddia/claude-for-strategyWrote 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/skills/daddia/claude-for-strategy/benefits-map)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/benefits-map"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/benefits-map/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/skills/daddia/claude-for-strategy/benefits-map"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/benefits-map.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.00067 | $0.01911 |
| Opus 5 | $0.00034 | $0.00955 |
| Sonnet 5 | $0.00013 | $0.00382 |
| Haiku 4.5 | $0.00007 | $0.00191 |
Grade A, and why
benefits-map 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Benefits Map
When to use
Decompose benefit claims into enabler → business change → benefit → strategic objective before register build.
What this skill does not do
- Does not set baselines — route to
/value-realisation:benefits-register. - Does not track actuals — route to
/value-realisation:benefits-tracking.
Preconditions
| Input | If missing |
|---|---|
| Practice profile | Proceed with default chain; [PROVISIONAL] |
| Source business case or strategic option | Build from user input; note SOURCE |
Provisional mode
Default enabler→change→benefit chain; conservative deadweight and cash-type flags.
Trust spine
Structured-aggregation bands; benefit-washing and deadweight checks; orphan/coverage gaps flagged.
Assumption audit
Before building chains, audit assumptions embedded in the source business case:
| Assumption | Status | If wrong, what breaks |
|---|---|---|
| Business change will occur as described | [named roles / generic / missing] | Benefit-washing undetected |
| Baseline will be captured before go-live | [committed / planned / unknown] | Register built on retrofitted numbers |
| Benefit type classification (cash vs non-cash) | [explicit / implied / wrong] | Headline value overstated |
| Deadweight / attribution | [considered / ignored / unknown] | Inflated initiative credit |
| Strategic objective linkage | [traced / asserted / orphan] | Portfolio alignment fiction |
Echo material assumptions in the output when status is not explicit or committed.
Red flags
Value-realisation mapping has non-negotiable quality gates:
- MUST NOT accept "system delivered" as a benefit — deliverables are enablers; missing business change causes benefit-washing.
- Do not proceed to register handoff if cash-releasable benefits are labeled as guaranteed cash-releasing — misclassification causes finance to book unrealised savings.
- Hard stop: orphan benefits with no strategic objective and no user acknowledgment — scope creep tends to cause unfunded workstreams.
- MUST NOT skip the deadweight check on quantified benefits — existing trends cause false attribution.
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 · 139 lines · 67 tokens per session scan A 2b7c7ce28227
benefits-map is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 1,911 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.