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 agentmods add commands/matteocervelli/llms/gh-milestone-creategit clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/gh-milestone-create)<a href="https://agentmods.dev/commands/matteocervelli/llms/gh-milestone-create"><img src="https://agentmods.dev/badge/commands/matteocervelli/llms/gh-milestone-create.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.00607 |
| Opus 5 | $0.00006 | $0.00303 |
| Sonnet 5 | $0.00003 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
gh-milestone-create 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 3d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create GitHub Milestone
Create a milestone on GitHub with title, description, and optional due date.
Usage
/gh-milestone-create # Interactive mode
/gh-milestone-create "Sprint 3" # With title
/gh-milestone-create "Sprint 3" 2025-11-15 # With title and due date
What it does
- Checks if GitHub CLI is authenticated
- Gets repository information
- Creates milestone with specified details
- Optionally sets due date
- Returns milestone URL and number
Execution
!echo "📋 Creating GitHub milestone..." !gh auth status !gh repo view --json nameWithOwner,url | grep -E 'nameWithOwner|url' !gh milestone create "New Milestone" --description "Milestone description" --due-date 2025-12-31
Interactive Example
For interactive milestone creation with prompts:
!gh api repos/:owner/:repo/milestones -f title="Sprint 3" -f description="Sprint 3 objectives" -f due_on="2025-11-15T23:59:59Z" -f state="open"
Parameters
- title (required): Milestone title
- description (optional): Detailed description of milestone goals
- due-date (optional): Due date in YYYY-MM-DD format
- state (optional): open or closed (default: open)
Examples
Basic milestone
/gh-milestone-create "v1.0 Release"
Milestone with due date
/gh-milestone-create "Q4 Goals" 2025-12-31
Using GitHub API directly
gh api repos/owner/repo/milestones \
-f title="Sprint 4" \
-f description="Complete core features" \
-f due_on="2025-11-30T23:59:59Z"
Listing Existing Milestones
gh milestone list
gh api repos/:owner/:repo/milestones
Requirements
- GitHub CLI (
gh) installed and authenticated - Write access to the repository
- Valid repository context
Tips
- Use clear, action-oriented milestone titles
- Set realistic due dates
- Include objectives in description
- Link issues to milestones for tracking
- Use milestones for sprint planning
- Close milestones when complete
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.
- 3d ago First seen · 93 lines · 13 tokens per session scan A 059b53c6590c
gh-milestone-create is a command published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 607 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-09-01.
Other commands, from other repositories
status
Generate a comprehensive project status report — active features, recent decisions, agent recommendations, and health assessment.
iterate
Execute a single Ralph loop iteration - complete one work unit from tasks.md with proper commits and progress tracking.
fd-done
Close the task — summarize built vs required, then commit and push on confirmation.
squash-pr
Squash branch commits into one clean commit and open a PR.
spawn-team
Spawn ClawTeam parallel workers for the current development phase.
wtfp:contribute
Guide a bounded WTF-P contribution from branch creation through a reviewable change request.