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 vosslab/vosslab-skills --skill old-orchestrate-next-milestonegit clone --depth 1 https://github.com/vosslab/vosslab-skillsWrote 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/vosslab/vosslab-skills/old-orchestrate-next-milestone)<a href="https://agentmods.dev/skills/vosslab/vosslab-skills/old-orchestrate-next-milestone"><img src="https://agentmods.dev/badge/skills/vosslab/vosslab-skills/old-orchestrate-next-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/vosslab/vosslab-skills/old-orchestrate-next-milestone"><img src="https://agentmods.dev/badge/skills/vosslab/vosslab-skills/old-orchestrate-next-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.00061 | $0.01450 |
| Opus 5 | $0.00030 | $0.00725 |
| Sonnet 5 | $0.00012 | $0.00290 |
| Haiku 4.5 | $0.00006 | $0.00145 |
Grade A, and why
old-orchestrate-next-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 12d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate Next Milestone
Overview
Execute the selected plan milestone to closure, not just partial checkboxes. Prioritize finishing the milestone with passing gates and clear evidence.
Terminology Alignment
- Milestone: primary planning unit with deliverables and gates.
- Workstream: parallel lane inside a milestone.
- Work package: coder-sized chunk with acceptance criteria and verification commands.
- Patch: reviewable code change set used in summaries and changelog entries.
- Stage / Step / Pass: durable pipeline terms for code identifiers when needed.
- If older plans use "phase", treat it as legacy milestone wording and do not introduce new phase terminology.
Operating mode
- Treat the manager-selected milestone as the primary target.
- Implement code, tests, and documentation updates required to close that milestone.
- Include adjacent fixes when they are necessary to pass milestone gates or prevent immediate regressions.
- Keep changes contract-driven and avoid case-specific hacks.
Inputs to read first
- Review STYLE guides in AGENTS.md, docs/PYTHON_STYLE.md, and docs/REPO_STYLE.md
- Manager directive naming the target milestone (or latest explicit manager instruction).
- Target plan in
docs/active_plans/(if present in the target repo; or use specified path). refactor_progress.mdfor active/completed context (if present in the target repo).- Related archive precedent if cited by the plan.
- Current repo state (
git status --short,git diff).
Mandatory constraints
- Decompose hard problems into atomic single-coder tasks per
docs/REPO_STYLE.md. - Treat the plan design philosophy near the top as binding architecture policy.
- Do not stop at partial progress when the remaining work is directly required to close the selected milestone.
- Do not ask for guidance before attempting concrete unblock steps.
- Do not weaken strict gates to force a pass.
- Do not move geometry/runtime policy into tool/report layers unless the plan explicitly requires it.
- Do not claim completion without reproducible command evidence.
What ships with it
1 file 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.
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.
- 12d ago First seen · 173 lines · 61 tokens per session scan A 0eaebcfd0536
old-orchestrate-next-milestone is a skill published in the GitHub repository vosslab/vosslab-skills (2 stars, last pushed 16d ago), licensed MIT. It adds 61 tokens to every session and 1,450 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…