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.
git 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/agents/daddia/claude-for-strategy/realisation-checkpoint-reminder)<a href="https://agentmods.dev/agents/daddia/claude-for-strategy/realisation-checkpoint-reminder"><img src="https://agentmods.dev/badge/agents/daddia/claude-for-strategy/realisation-checkpoint-reminder/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/agents/daddia/claude-for-strategy/realisation-checkpoint-reminder"><img src="https://agentmods.dev/badge/agents/daddia/claude-for-strategy/realisation-checkpoint-reminder.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.00055 | $0.00505 |
| Opus 5 | $0.00028 | $0.00253 |
| Sonnet 5 | $0.00011 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
realisation-checkpoint-reminder 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 5d 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Realisation Checkpoint Reminder
Runs monthly by default (9am on the 1st) — override to match the practice profile's recorded tracking cadence if it differs from monthly.
What it does
-
Reads the current benefits register and tracking log. Identifies which benefits are due for a
benefits-trackingrun this cycle, based on the profile's tracking cadence. -
Prompts the benefit owner(s) via
~~chatthat tracking is due, and pulls the most recent measured value it can access to pre-stage the run rather than starting from nothing. -
Separately, and with higher urgency, scans the register for any benefit whose business change is scheduled to go live — or has already gone live — within the practice profile's baseline window, with no baseline value yet recorded. This is escalated distinctly from the ordinary tracking reminder above, with an explicit note explaining why: once the business change starts, a clean pre-change baseline can no longer be captured, and the benefit's realisation claim becomes permanently harder to prove. This check should fire even between scheduled tracking cycles if a go-live date is close.
-
Compiles a summary for the benefits owner or value-realisation lead, surfacing:
- Benefits due for tracking this cycle.
- Any benefit with a missing-baseline escalation (flagged separately and first).
- Any benefit that didn't respond to last cycle's tracking prompt (silence on a due tracking run is itself worth noting, not just re-prompting silently).
Fallback with no ~~chat connected
Without a chat connector, this agent can't push prompts to individual owners. It should still run its read side — compile the due-tracking list and, especially, the missing-baseline escalation — and surface that summary directly in the conversation or as a note for the value-realisation lead to distribute manually. The missing-baseline check in particular should never be silently skipped; a degraded reminder is better than a missed baseline.
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.
- 5d ago First seen · 32 lines · 55 tokens per session scan A eb3b388576e3
realisation-checkpoint-reminder is an agent published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 505 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 agents, from other repositories
conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
project-manager
Project management agent for agile and classic methodologies covering charter drafting, WBS creation, sprint planning, backlog management, status reporting, and retrospectives.
ndv-scope
Scope enforcer. Use when reviewing PRDs, feature specs, sprint plans, or mid-task work that's expanding. Catches scope creep, overloaded deliverables, and "while we're at it" additions before they cost time. Autistic intolerance of undefined boundaries — undefined scope is not a risk to be managed, it is a state that…
Task Manager
Goal-oriented agent for managing tasks, priorities, and project execution.
drupal-tech-lead
Use this agent when you need expert Drupal technical leadership for architecture decisions, team coordination, and project governance. Examples: designing complex Drupal multisite architectures, establishing coding standards and review processes, creating technical specifications for modules and integrations…