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 milestone-trackergit 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/milestone-tracker)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/milestone-tracker"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/milestone-tracker.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.00055 | $0.00765 |
| Opus 5 | $0.00028 | $0.00382 |
| Sonnet 5 | $0.00011 | $0.00153 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
milestone-tracker 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Milestone Tracker
When to use
Critical-path milestone status with slippage against profile tolerance — knock-on effects, not flat date lists.
What this skill does not do
- Does not invent progress — ask for plan and actuals.
- Does not escalate non-critical float slips — distinguish timeline threats from noise.
Preconditions
| Input | If missing |
|---|---|
| Milestone plan | Ask — halt if absent |
| Current actuals/forecast | Ask — don't infer |
| Slippage tolerance (profile) | Default with [PROVISIONAL] |
Provisional mode
Partial actuals: assess available milestones; flag incomplete coverage.
Trust spine
- Confidence bands (
governance-tracking):- High: Critical path identified; slippage classified; knock-on effects stated.
- Medium: Some forecasts uncertain — tagged
[review]. - Low: Plan missing — halt.
- Failure modes:
- Incentive Gaming: N/A — schedule focus.
- Escalation triggers: Critical-path slip beyond tolerance — overall end date at risk.
Workflow
- Read profile for plan location and slippage tolerance.
- Get plan and actuals.
- Identify critical path vs float.
- Classify each critical milestone: on track / at risk / slipped.
- State knock-on effects for at-risk/slipped items.
- Note non-critical items briefly without escalation.
- Gaming-pattern check before output.
Output format
CONFIDENCE: [defensible recommendation | structured first pass]
CRITICAL PATH STATUS:
[Milestone] — Planned: [date] | Actual/Forecast: [date] | Status: [...]
Knock-on effect: [...]
NON-CRITICAL (float available): [...]
OVERALL END DATE: [on track | at risk | slipped] — [why]
Worked example
Input: Integration milestone 2 weeks late on critical path; QA milestone 1 week late with float.
Expected output: Integration slipped with end-date knock-on; QA noted non-critical only.
Quality checks before delivering
- Critical path distinguished from float
- Tolerance from profile applied
- Knock-on effects for critical slips
- No invented actuals
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 · 93 lines · 55 tokens per session scan A f3fc68afc32e
milestone-tracker is a skill 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 765 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.
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.