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 realisation-reviewgit 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/realisation-review)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/realisation-review"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/realisation-review/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/realisation-review"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/realisation-review.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.00070 | $0.01318 |
| Opus 5 | $0.00035 | $0.00659 |
| Sonnet 5 | $0.00014 | $0.00264 |
| Haiku 4.5 | $0.00007 | $0.00132 |
Grade A, and why
realisation-review 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Realisation Review
When to use
End-of-window planned-vs-actual portfolio review — optimism-bias calibration across initiatives.
What this skill does not do
- Does not re-litigate LAPSED reasons — carry forward from
benefits-recovery. - Does not blend benefit types in one headline cash figure.
Preconditions
| Input | If missing |
|---|---|
| Full register + tracking history | Ask |
| Prior realisation reviews (optional) | Skip optimism-bias cross-review |
Provisional mode
Single-initiative review without portfolio history — note optimism-bias check limited.
Trust spine
Narrative-synthesis BLUF; root-cause cluster diagnosis; calibration discount for future cases.
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 full benefits register, the complete tracking history, and anybenefits-recoverydecisions for benefits in the window under review. -
Score each benefit: REALISED IN FULL / PARTIALLY REALISED (state the percentage) / NOT REALISED / LAPSED (carry forward the specific reason recorded in
benefits-recovery, don't re-litigate it here). -
Roll up to portfolio level — total planned value vs. total realised value, split by type. Report cash-releasing, cash-releasable, and non-cash/qualitative separately; don't blend them into one headline figure. If any cash-releasable benefit was treated as guaranteed cash anywhere in the original case or subsequent reporting, call that out explicitly here — it's a common and material distortion in how a portfolio's "savings" get represented upward.
-
Run the optimism-bias check. If prior
realisation-reviewruns exist for other initiatives, compare this initiative's realisation rate to the pattern across those reviews. A single underperforming initiative may just be that initiative's story; a consistent realisation rate well below 100% across multiple independent reviews is a finding about how this organization's business cases get sized, and should be named as such rather than absorbed case-by-case. If a pattern emerges, state a suggested calibration discount for future business case estimates and flag it as a direct input totransformation:business-caseorcorporate-strategy:evaluate-strategic-option.
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 · 105 lines · 70 tokens per session scan A 5faefa88b096
realisation-review is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 1,318 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.