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-recoverygit 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-recovery)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/benefits-recovery"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/benefits-recovery/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-recovery"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/benefits-recovery.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.00072 | $0.01438 |
| Opus 5 | $0.00036 | $0.00719 |
| Sonnet 5 | $0.00014 | $0.00288 |
| Haiku 4.5 | $0.00007 | $0.00144 |
Grade A, and why
benefits-recovery 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 9d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Benefits Recovery
When to use
At-risk benefits — root-cause split and continue-vs-write-down without sunk-cost bias.
What this skill does not do
- Does not remeasure — uses tracking history from
benefits-tracking. - Does not edit register silently — write-down updates register with reason.
Preconditions
| Input | If missing |
|---|---|
| Register entry + tracking history | Ask |
| Practice profile | Default conservative recovery test |
Provisional mode
Marginal cost/remaining value estimates tagged [review] when data thin.
Trust spine
Option-evaluation bands; sunk-cost bias flagged; MEASUREMENT LAG stand-down honored.
Workflow
-
Read the practice profile —
~/.claude/plugins/config/claude-for-strategy/org-profile.mdand~/.claude/plugins/config/claude-for-strategy/value-realisation/CLAUDE.md— the benefit's register entry, and its full tracking history — the pattern across periods matters more than the most recent number alone. -
Run the diagnostic split. Classify the root cause as exactly one of:
- MEASUREMENT LAG — too little time has passed since the business change to expect the benefit to show up yet. Not actually at risk; say so and stand down the escalation rather than treating every early AT-RISK flag as real trouble.
- NOT EMBEDDED — the business change itself wasn't adopted: training didn't land, the old process is still being used alongside or instead of the new one, the system is live but unused as designed. The fix is adoption work, not redesign.
- ENABLER GAP — the underlying capability was descoped, delayed, or built differently than the benefit map assumed. The fix is closing the capability gap, not pushing harder on adoption of something that isn't actually there yet.
- THEORY PROBLEM — the business change was embedded as designed, the enabler works as built, and the benefit still hasn't moved. The causal assumption made back in
benefits-mapwas wrong. This needs revisiting the map's logic, not more push on execution that was never the actual gap — say this plainly even though it's the less comfortable conclusion. - STRUCTURALLY LOST — the realisation window has passed, or the business conditions the original case assumed no longer hold (the market moved, the cost line was restructured for unrelated reasons first). The benefit cannot be recovered as originally framed, regardless of further effort.
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.
- 9d ago First seen · 111 lines · 72 tokens per session scan A 4d91530f5461
benefits-recovery is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 1,438 once invoked, about $0.0004 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
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.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
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.
nx-monorepo
Provides comprehensive Nx monorepo management guidance for TypeScript/JavaScript projects. Use when creating Nx workspaces, generating apps/libraries/components, running affected commands, setting up CI/CD, configuring Module Federation, or implementing NestJS backends within Nx.