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 alunduil/alunduil-chezmoi --skill milestonesgit clone --depth 1 https://github.com/alunduil/alunduil-chezmoiWrote 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/alunduil/alunduil-chezmoi/milestones)<a href="https://agentmods.dev/skills/alunduil/alunduil-chezmoi/milestones"><img src="https://agentmods.dev/badge/skills/alunduil/alunduil-chezmoi/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/alunduil/alunduil-chezmoi/milestones"><img src="https://agentmods.dev/badge/skills/alunduil/alunduil-chezmoi/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.00094 | $0.01794 |
| Opus 5.5 | $0.00038 | $0.00718 |
| Sonnet 5.5 | $0.00019 | $0.00359 |
| Haiku 4.5 | $0.00009 | $0.00179 |
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 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Milestones
A milestone is one objective for one calendar month. Its issues are the work; its key results say whether the objective landed. Write and score them to Google's OKR playbook.
Shape
-
Title:
YYYY-MM: <objective>— e.g.2026-11: Secrets resolve from 1Password on every host. The month prefix sorts and filters; the objective reads in issue sidebars. -
Due date: last day of the month.
-
Description:
<One or two present-tense sentences expanding the title's objective.> Type: committed | aspirational As measured by: - [ ] <key result> - [ ] <key result> Non-goals: <optional, one line bounding scope>
Writing the objective
The objective states the outcome at month end.
- Fits in the title, and a rational observer can tell whether it landed.
- Names a benefit to someone outside the work: the user at a host, a reader, a contributor. Test: could every key result score 1.0 with nobody better off? Then reword it around the benefit.
- Starts from what that person needs. Maintenance of what the repo already does stays out of milestones.
Writing key results
Key results are measurable outcomes that prove the objective.
- Each states an outcome with its evidence: a command that passes, a count that hits a number, an observable state. A verb like consult, help, analyse, or participate marks an activity; restate it as what the activity produces.
- Name the effect a user sees. A release, merge, or launch counts only as evidence of that effect.
- A grader scores it 0.0–1.0 at month end without asking the author. Say how partial credit is counted when it isn't obvious: for example, 9 of 12 repositories scores 0.75.
- Together they are sufficient: 1.0 on all of them means the objective landed. Add or rework key results until that holds.
- Two to four per objective.
- Date a key result that lands before month end (
by 2026-11-14). Every key result due on the last day means the plan isn't real yet.
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 · +12 lines 784aa5c74f7a
- 16d ago Changed · +67 lines · +43 tokens per session a761e468dfdc
- 1mo ago First seen · 105 lines · 51 tokens per session scan A 948eb62672cc
milestones is a skill published in the GitHub repository alunduil/alunduil-chezmoi (2 stars, last pushed today), licensed 0BSD. It adds 94 tokens to every session and 1,794 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
acli
Search, plan, and update Atlassian Jira and Confluence with acli.
github-issues
Plan, draft, update, link, and close GitHub issues.
project-manager
Use when creating, updating, or triaging GitHub issues. Writes issues from a product perspective — user stories, acceptance criteria, context, and dependencies — without prescribing implementation.
share-plan
Use when sharing an implementation plan to a GitHub issue. Formats plans with collapsible details sections so issues are scannable but comprehensive.
podio-ticket-updates
Sync in-progress Podio Kanban tickets with progress from their linked GitHub repos — propose description updates and progress comments, apply after approval. Use when the user asks to update Podio tickets, sync ticket progress, or post status updates to the Kanban board.
work-on
Ship a GitHub issue end to end by assessing complexity and composing the available research, planning, implementation, review, commit, and pull-request workflows.