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 granoflow/granoflow-mcp-server --skill granoflow-milestone-coordinationgit clone --depth 1 https://github.com/granoflow/granoflow-mcp-serverWrote 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/granoflow/granoflow-mcp-server/granoflow-milestone-coordination)<a href="https://agentmods.dev/skills/granoflow/granoflow-mcp-server/granoflow-milestone-coordination"><img src="https://agentmods.dev/badge/skills/granoflow/granoflow-mcp-server/granoflow-milestone-coordination/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/granoflow/granoflow-mcp-server/granoflow-milestone-coordination"><img src="https://agentmods.dev/badge/skills/granoflow/granoflow-mcp-server/granoflow-milestone-coordination.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.00052 | $0.02493 |
| Opus 5 | $0.00026 | $0.01247 |
| Sonnet 5 | $0.00010 | $0.00499 |
| Haiku 4.5 | $0.00005 | $0.00249 |
Grade A, and why
granoflow-milestone-coordination 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 10d 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Granoflow Milestone Coordination
Use this Skill when milestones and (usually) child tasks already exist and the user wants to charter, coordinate, replan, prove integration, or close one active milestone. Child Task Work owns local Analysis, Planning, execution, and Delivery.
Do not use this Skill to create the project milestone portfolio or to
author task titles/descriptions. Use granoflow-milestone-workflow,
granoflow-task-authoring, and granoflow-portfolio-orchestrator for that.
Keyword
#milestone-coordination#milestone-charter#milestone-close
When To Use
- Milestone entities exist (from milestone-workflow or portfolio orchestrator).
- The user asks to coordinate, continue, integrate, or close an active milestone.
- Child tasks may still be split/merged/reordered inside a confirmed charter.
Ownership Boundary
- The Granoflow App and Local HTTP API remain authoritative for the milestone, controller Task, child tasks, and completion summary.
- Until Granoflow exposes milestone attachments, one controller Task bound to the milestone owns the complete Milestone Work attachment. The active milestone description contains only the concise living summary and controller Task reference.
- Each child task owns its Task Work, Delivery, and local execution history.
- The MCP server stays a thin workflow and API adapter.
Workflow
At entry, call granoflow_agent_preferences_get(projectId) once. Preferences
never weaken Task Work, test, Delivery, authorization, acceptance, or
external-action gates.
1. Resolve The Active Milestone And Its Controller
Read the project, active milestone, description, completion summary, controller Task, child tasks, Task Work/Delivery references, and context pack. If more than one active target remains plausible, stop before writing.
If no controller Task exists, preview one whose sole responsibility is orchestration, integration evidence, and closeout—not child implementation.
Checkpoints:
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.
- 10d ago First seen · 254 lines · 52 tokens per session scan A a2f7fe9f3e69
granoflow-milestone-coordination is a skill published in the GitHub repository granoflow/granoflow-mcp-server (0 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 2,493 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.