Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add kenmulford/milestone-driver/plugin install milestone-driverWrote 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/kenmulford/milestone-driver/solve-milestone)<a href="https://agentmods.dev/skills/kenmulford/milestone-driver/solve-milestone"><img src="https://agentmods.dev/badge/skills/kenmulford/milestone-driver/solve-milestone/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/kenmulford/milestone-driver/solve-milestone"><img src="https://agentmods.dev/badge/skills/kenmulford/milestone-driver/solve-milestone.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.00129 | $0.08199 |
| Opus 5 | $0.00064 | $0.04099 |
| Sonnet 5 | $0.00026 | $0.01640 |
| Haiku 4.5 | $0.00013 | $0.00820 |
Grade B, and why
solve-milestone scanned grade B with 1 finding 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 today.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
| 1 | `~/.claude/settings.json` (user global) | How it starts
The opening of the file, as written. The whole thing — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
solve-milestone - autonomous driver
Order a milestone's issues, run /milestone-driver:solve-issue on each, integrate to integrationBranch between issues. Owns ordering, the loop, branch re-sync, parking, the final summary; solve-issue owns the per-issue pipeline.
Coherence pass (coherenceReviewAgent, read-only, never gates). Runs per-issue in solve-issue section 6, before that issue's /code-review. Under wave granularity it runs instead at the Phase-2 merge-tail re-verify point (skills/solve-milestone/parallel-waves.md § Parallel mode - Phase 2: serial verified merge tail), against the integrated wave. Absent → skip silently.
Blast radius. Merge only to integrationBranch, never protectedBranch. Release, closing the milestone object, and deploy are human-only. This skill closes the milestone's issues and authors the CHANGELOG; never the milestone.
Execution mode: parallel by default. No flag, no opt-in. Resolved once at run start by the barrier cascade in the last Before-starting step (Resolve execution mode), then held all run. A typed --parallel, or "in parallel", in $ARGUMENTS is stripped and ignored by step 3's --<token> strip.
Contents
Before starting · The procedure - 1. List the milestone's open issues · 2. Determine the order · 3. Determine the target version · Phase 0 - Triage · 4. Loop over issues in dependency-graph order · Permission pre-flight gate · Simplify pass · 5. Finish · Autonomy · Output spec - Template 1 - Run start / plan board · Template 2 - Status update at each wave boundary · Template 3 - Final results · Output style - Main-thread context · Final summary - 6. Author the CHANGELOG entry · Run-complete notification
Before starting
- Auth preflight. Run
gh auth status. Non-zero exit, or output containing "not logged in" / "authentication failed" → printError: gh auth status failed - authenticate with 'gh auth login' before running solve-milestone.and halt. - Read the profile (
docs/profile-schema.md).
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- abandoned-recovery.md 4.8 KB
- blocked-label-clear.md 2.2 KB
- changelog-authoring.md 14 KB
- contingencies.md 7.6 KB
- db-hazard-interview.md 2.2 KB
- integration-granularity.md 14 KB
- md-epic-parent-check.md 2.2 KB
- milestone-granularity.md 23 KB
- not-buildable.md 3.2 KB
- parallel-waves.md 39 KB
- sequential-loop.md 6.8 KB
- simplify-pass.md 11 KB
- trello-sync.md 17 KB
- version-target.md 2.6 KB
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.
- today Changed ff3e590ffd67
- 8d ago First seen · 320 lines · 129 tokens per session scan B d0e48be71ec6
solve-milestone is a skill published in the GitHub repository kenmulford/milestone-driver (2 stars, last pushed today), licensed MIT. It adds 129 tokens to every session and 8,199 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
contribute-to-eliza
Finish and prove a scoped elizaOS GitHub issue, or independently review and repair an open elizaOS pull request. Use when contributing compute to elizaOS by selecting unclaimed work, implementing or reviewing changes, adding real tests and evidence, validating artifacts, or preparing a contribution for maintainer…
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
pr-comment
Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review. Use when: posting code review comments, giving PR feedback, sending inline suggestions. Not for: reading existing reviews (use load-pr-review), creating PRs (use create-pr), PR status (use pr-summary).
pr-fixer
Trigger the Amber Handler to automatically fix a pull request (rebase, address review comments, run lints/tests, push fixes). Posts @ambient-code on the PR to trigger the fix prompt. Use when user types /pr-fixer , says "fix PR", "run pr-fixer", "address PR comments", or "auto-fix pull request".