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 deevus/tea-skills --skill milestonesgit clone --depth 1 https://github.com/deevus/tea-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/deevus/tea-skills/milestones)<a href="https://agentmods.dev/skills/deevus/tea-skills/milestones"><img src="https://agentmods.dev/badge/skills/deevus/tea-skills/milestones/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/deevus/tea-skills/milestones"><img src="https://agentmods.dev/badge/skills/deevus/tea-skills/milestones.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.00025 | $0.00397 |
| Opus 5 | $0.00013 | $0.00198 |
| Sonnet 5 | $0.00005 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
milestones 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 9d 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
Milestones
List
tea milestones list -o simple # open milestones, compact output (recommended)
tea milestones list --state all -o simple # include closed
tea milestones list --output json # use json only when parsing is necessary
tea milestones list --fields "title,state,items_open,items_closed,duedate,description"
Show
tea milestones "v1.0"
Create
tea milestones create # interactive
tea milestones create --title "v1.0" --description "First stable release"
tea milestones create --title "v1.0" --deadline "2025-06-01" # with due date
Close / Reopen / Delete
tea milestones close "v1.0" # or multiple: close "v0.8" "v0.9"
tea milestones reopen "v1.0"
tea milestones delete "v1.0"
Edit
The tea CLI doesn't have a milestone edit command. For the bundled action, see actions/milestones/README.md.
When resolving actions/... paths, use the actions/ directory bundled relative to this skill directory.
Pass explicit scope flags (--login, --remote, or --repo) to bundled actions when the user names a login, remote, backend, or repository. Otherwise, bundled actions use active-host-first discovery.
Tips
- Milestones are identified by name in CLI, by ID in the API-backed milestone edit action
- Deadlines accept date strings like
2025-06-01 - Deleting a milestone doesn't close its issues — they just become unassigned
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.
- 9d ago First seen · 54 lines · 25 tokens per session scan A db252d93b679
milestones is a skill published in the GitHub repository deevus/tea-skills (8 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 397 once invoked, about $0.0001 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
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
parallel-work-check
Apply before starting work on an existing branch. Checks for parallel work by other agents or developers that may supersede or conflict with your planned changes. Prevents wasted effort on stale branches.
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.