Borrowing it
Nothing to install: this file belongs to frostney/GocciaScript. 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/frostney/GocciaScript/main/.agents/skills/milestone-rush/SKILL.mdgit clone --depth 1 https://github.com/frostney/GocciaScriptWrote 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/frostney/gocciascript/milestone-rush)<a href="https://agentmods.dev/skills/frostney/gocciascript/milestone-rush"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/milestone-rush/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/frostney/gocciascript/milestone-rush"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/milestone-rush.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.00064 | $0.02730 |
| Opus 5.5 | $0.00026 | $0.01092 |
| Sonnet 5.5 | $0.00013 | $0.00546 |
| Haiku 4.5 | $0.00006 | $0.00273 |
Grade A, and why
milestone-rush 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 yesterday.
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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Milestone rush
Finish the named milestone from its actual current state. Own the coordinated work-item deliveries and the release at the verified milestone boundary.
Authority and gates
- Require an exact repository and milestone. An explicit invocation authorizes scoped issue comments and replacement issues, branches and worktrees, implementation, validation, commits, plain pushes, pull requests, review remediation, squash merges, configured integration delivery, the milestone's configured release path, branch cleanup, and closing that milestone.
- Accept either a confirmed
/roadmap-reviewhandoff or direct invocation. For direct invocation, verify current scope, direction, readiness, dependencies, and measures of success before executing. Stop for material replanning rather than silently changing the milestone, for example for a closure that records a material rejected or deferred product decision, or a material scope expansion. - Treat a confirmed roadmap item as the mini-spec for
/deliveronly when it states the outcome, scope and non-goals, and testable measures of success. - Respect project instructions, Definitions of Ready and Done, branch
protection, review policy, and the remote default branch. Never amend, bypass
a gate, or overwrite unrelated work. Ordinary branches remain merge-only;
only
git-workflowmay apply its guarded native-stack rewrite exception. - Before planning or spawning, read and validate repository-root
ORCHESTRATION.mdunder references/orchestration.md. Then start the ignored event ledger by passing the run's first lifecycle event to theingestcommand under references/event-ledger.md before the first issue, PR, or worker action, even when the run then stops at a prerequisite. When the host exposes ingestion as a ledger or telemetry operation instead of a shell, use it; only when neither exists, report the ledger as unavailable.
What ships with it
5 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.
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.
- yesterday Changed · +3 lines abb6f9dca665
- 3d ago Changed · +2 lines 85e454c061c5
- 11d ago Changed · +2 lines 42ab767559c3
- 22d ago Changed · +3 lines 3b5e8c7139fa
- 25d ago First seen · 211 lines · 64 tokens per session scan A 00c8b554b5c3
milestone-rush is a skill published in the GitHub repository frostney/GocciaScript (20 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 2,730 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
stacking-prs
Create and manage GitHub native Stacked PRs in this repo with the gh stack CLI. Use when asked to stack PRs, split a large change into a stack, add a layer to a stack, restack or rebase a stack, adopt existing branches or PRs into a stack, check out someone else's stack, or land a stack. Covers creating and submitting…
ct-dev-workflow
Development workflow orchestration for task-driven development with atomic commits, conventional commit messages, and systematic release processes. Enforces task traceability, branch discipline, smart test scope selection, and GitHub Actions integration. Use when committing code, creating releases, managing branches…
smith-build
Autonomous build phase — generates tasks, implements, tests, commits, pushes, merges, and produces release notes. Runs without user interaction.
auto-build-loop
Autonomous build driver after SDD spec approval: phase-scoped headless build sessions, driver-owned commits, cross-provider review gates, milestone pauses, and fail-closed escalation — under explicit opt-in autonomy profiles.
github-ops
Fast GitHub operations via the gh CLI. Use when the user mentions GitHub issues, PRs, repos, actions, releases, creating or triaging issues, opening or reviewing pull requests, managing branches, inspecting repo state, or checking CI. Works on any repo the operator's gh CLI is authenticated against.