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-registergit 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-register)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/benefits-register"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/benefits-register/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-register"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/benefits-register.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.00066 | $0.01250 |
| Opus 5 | $0.00033 | $0.00625 |
| Sonnet 5 | $0.00013 | $0.00250 |
| Haiku 4.5 | $0.00007 | $0.00125 |
Grade A, and why
benefits-register 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 8d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Benefits Register
When to use
Turn mapped benefits into register entries — baseline, target, owner distinct from delivery PM.
What this skill does not do
- Does not accept retrofitted baselines as clean — RETROFITTED BASELINE flag carries forward.
- Does not duplicate metric definitions — hand off to
performance:metrics-glossarywhen installed.
Preconditions
| Input | If missing |
|---|---|
benefits-map output |
Ask user to map first or provide chain |
| Practice profile baseline discipline | Flag conservatively |
Provisional mode
Owner same as PM → governance gap flag, not silent default.
Trust spine
Structured-aggregation bands; baseline-before-change enforced; double-counting checked.
Workflow
-
Read the practice profile —
~/.claude/plugins/config/claude-for-strategy/org-profile.mdand~/.claude/plugins/config/claude-for-strategy/value-realisation/CLAUDE.md— for the baseline-discipline answer from setup and the benefit type taxonomy, and readbenefits-mapoutput for the benefit chain being registered. -
For each benefit, capture:
- Measure — the exact formula, not a description. If
performanceis installed, hand off the formal metric definition toperformance:metrics-glossaryand reference it here rather than duplicating it — same seam pattern asokr:instrument-metricsandbalanced-scorecard:select-measures. This skill owns the benefit-to-measure mapping, the baseline, and the accountability assignment, not the metric's formal definition. - Baseline value, baseline date, and baseline source.
- Target value and realisation date — the date the benefit is expected to be fully realised, which is usually later than go-live; don't let the two dates collapse into one without asking.
- Benefit type — carried forward from
benefits-map.
- Measure — the exact formula, not a description. If
-
Enforce baseline-before-change, explicitly. Compare the baseline date to the business change's go-live date (or planned go-live, if not yet live):
- Baseline date clearly precedes go-live → clean.
- Baseline date is on or after go-live, or no baseline exists and the change has already gone live → flag as RETROFITTED BASELINE. State plainly that this benefit's realisation claim is now compromised — any apparent improvement from this point can no longer be cleanly separated from improvement that may have already happened before measurement started. Don't record a retrofitted baseline as if it were a normal one; the flag should travel with this benefit into every later tracking cycle.
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.
- 8d ago First seen · 98 lines · 66 tokens per session scan A ed57d95c2fe3
benefits-register is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 1,250 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
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.