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/slippage-watcher)<a href="https://agentmods.dev/agents/daddia/claude-for-strategy/slippage-watcher"><img src="https://agentmods.dev/badge/agents/daddia/claude-for-strategy/slippage-watcher.svg" alt="Measured on agentmods" 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.00038 | $0.00415 |
| Opus 5 | $0.00019 | $0.00208 |
| Sonnet 5 | $0.00008 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
slippage-watcher 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 4d 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.
What it actually says
Slippage Watcher
Runs weekly by default (Wednesday 09:00) — override the schedule to match the milestone-check cadence recorded in the practice profile if it differs.
What it does
-
Reads the practice profile for where the milestone plan lives and the slippage tolerance — how much delay before something is "at risk" vs. slipped vs. just noted.
-
Gets the milestone plan and current actuals/forecasts from wherever the profile points (pasted markdown,
~~spreadsheet,~~project tracker, etc.). Do not infer progress from partial information. -
Identifies critical-path milestones — which delays push out the end date versus which have float.
-
Compares planned vs. actual/forecast on each critical-path milestone and applies the profile tolerance. Flag items at risk (within tolerance but trending late) and slipped (beyond tolerance).
-
For every at-risk or slipped item, states the knock-on effect — what downstream milestone or the overall end date is now threatened, not just that this one date moved.
-
Posts the summary to
~~chat. If no chat connector is configured, write the summary to a file in the workspace instead. -
Includes an all-clear footer when nothing is at risk or slipped on the critical path. The footer means the agent ran — non-critical items with float may still have moved without warranting escalation.
Fallback with no ~~chat connected
If no chat connector is configured, still run the read side — compare plan vs. actual, apply tolerance, and write the slippage summary (or all-clear) to a file. Do not silently skip the run.
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.
- 4d ago First seen · 34 lines · 38 tokens per session scan A fb1f56abaefa
slippage-watcher is an agent published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 415 once invoked, about $0.0002 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…