Borrowing it
Nothing to install: this file belongs to VelimirMueller/vlm-code-context-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/VelimirMueller/vlm-code-context-mcp/main/.claude/commands/milestone.mdgit clone --depth 1 https://github.com/VelimirMueller/vlm-code-context-mcpWrote 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/commands/velimirmueller/vlm-code-context-mcp/milestone)<a href="https://agentmods.dev/commands/velimirmueller/vlm-code-context-mcp/milestone"><img src="https://agentmods.dev/badge/commands/velimirmueller/vlm-code-context-mcp/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/commands/velimirmueller/vlm-code-context-mcp/milestone"><img src="https://agentmods.dev/badge/commands/velimirmueller/vlm-code-context-mcp/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.00000 | $0.00479 |
| Opus 5.5 | $0.00000 | $0.00192 |
| Sonnet 5.5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
milestone 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 1mo 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
/milestone — Milestone Management
Create, update, and close milestones using MCP tools.
Step 0 — Load Context (1-2 calls)
get_resume_state() # project state, milestones, epics
Deferred — use load_phase_context() when needed
| Action | Call |
|---|---|
| View epics for milestone | load_phase_context({ phase: "epics" }) |
| Estimate remaining sprints | load_phase_context({ phase: "tickets" }) (has velocity) |
| Review discovery coverage | load_phase_context({ phase: "discovery" }) |
View milestones
Already loaded in Step 0. Display the data from get_resume_state().
Update milestone progress
update_milestone({ milestone_id: <id>, progress: <0-100> })
Close / complete a milestone
First verify all epics are done (use data from Step 0):
list_epics({ milestone_id: <id> })
Only close if ALL epics linked to it are completed:
update_milestone({ milestone_id: <id>, status: "completed", progress: 100 })
Update milestone details
update_milestone({ milestone_id: <id>, description: "...", target_date: "2026-05-01" })
Link a sprint to a milestone
# Via sprint creation
start_sprint({ ..., milestone_id: <id> })
# Or update existing sprint
update_sprint({ sprint_id: <id>, milestone_id: <id> })
Link epic to milestone
create_epic({ name: "...", description: "...", milestone_id: <id> })
Rules
- Context first. Always load from MCP DB before acting. Never assume state.
- Code context before file reads. Use
search_files()andget_file_context({ include_changes: false })before anyReadtool call. - Surface anomalies. Flag milestones past target date, epics with no progress, or discoveries not yet implemented.
- Verify before closing. Never close a milestone without checking all epics are completed.
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.
- 1mo ago First seen · 73 lines · 0 tokens per session scan A 6987d4392fe9
milestone is a command published in the GitHub repository VelimirMueller/vlm-code-context-mcp (5 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 479 tokens. 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-08-31.
Other commands, from other repositories
backlog-from-demo
Turn a recorded product demo into a prioritized backlog with timestamped evidence.
onplana-connect
Sign in to the Onplana MCP server, then verify it works.
staff-event
Build a complete event staffing plan (configured-market match, W-2 rates, tier-based lead time, compliance) and prepare a buyer-submitted quote form.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.