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 skills/qauth-labs/qauth/set-milestonenpx skills add qauth-labs/qauth --skill set-milestonegit clone --depth 1 https://github.com/qauth-labs/qauthWrote 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/qauth-labs/qauth/set-milestone)<a href="https://agentmods.dev/skills/qauth-labs/qauth/set-milestone"><img src="https://agentmods.dev/badge/skills/qauth-labs/qauth/set-milestone.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.1 | $0.00020 | $0.00460 |
| Opus 5 | $0.00010 | $0.00230 |
| Sonnet 5 | $0.00004 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
set-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 5d 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
Set Issue Milestone
Add or update the milestone on a GitHub issue.
Your Task
Manage milestones on issues.
List Available Milestones
gh api repos/{owner}/{repo}/milestones --jq '.[] | "\(.number): \(.title) (\(.state))"'
Set Milestone on Issue
# Using gh issue edit (recommended)
gh issue edit {issue_number} --milestone "MVP"
Remove Milestone
gh issue edit {issue_number} --remove-milestone
Create New Milestone
gh api repos/{owner}/{repo}/milestones \
-f title="v1.0" \
-f description="First release milestone" \
-f due_on="2026-06-01T00:00:00Z" \
-f state="open"
Update Milestone
# Get milestone number first
gh api repos/{owner}/{repo}/milestones --jq '.[] | select(.title=="MVP") | .number'
# Update milestone
gh api repos/{owner}/{repo}/milestones/{milestone_number} \
-X PATCH \
-f description="Updated description" \
-f state="open"
Close Milestone
gh api repos/{owner}/{repo}/milestones/{milestone_number} \
-X PATCH \
-f state="closed"
Bulk Set Milestone
# Set milestone on multiple issues
gh issue edit 1 2 3 4 5 --milestone "MVP"
Project Milestones
Current milestone is MVP; see github-conventions for the phase list.
Instructions
- List available milestones if user is unsure
- Use
gh issue editto set the milestone - Confirm the change was applied
- For new milestones, use the API to create them first
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.
- 5d ago First seen · 82 lines · 20 tokens per session scan A 6fe8246ac99d
set-milestone is a skill published in the GitHub repository qauth-labs/qauth (24 stars, last pushed 5d ago), licensed Apache-2.0. It adds 20 tokens to every session and 460 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-30.
Other skills, from other repositories
update-portal-ui
Guidelines for updating or designing pages in the portal React frontend (portal/src). Covers component conventions, link rendering rules, i18n patterns, and common pitfalls.
write-e2e-test
Write end-to-end (e2e) tests for authgear-server. Use when the user asks to write, add, or create e2e tests. The tests live in e2e/tests/ and are YAML-driven.
add-portal-screen
Add screens or components to the portal frontend. Use when the user asks to create a new portal page, screen, tab, or UI component.
api-design
Review or design APIs for Authgear. In review mode, evaluates a design draft against the checklist. In ideation mode, develops a design from a description and self-reviews it.
new-siteadmin-api
Full pipeline for adding a new Site Admin API feature — from OpenAPI spec through implementation plan to working service. Use when adding a new endpoint or filling in real data for an existing stub.
update-feature-config
Add or change a feature config field/section in pkg/lib/config (authgear.features.yaml). Use when adding a new feature config field, adding a new top-level section, or touching an existing section's Merge implementation.