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 joshukraine/dotfiles --skill autopilot-triagegit clone --depth 1 https://github.com/joshukraine/dotfilesWrote 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/joshukraine/dotfiles/autopilot-triage)<a href="https://agentmods.dev/skills/joshukraine/dotfiles/autopilot-triage"><img src="https://agentmods.dev/badge/skills/joshukraine/dotfiles/autopilot-triage/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/joshukraine/dotfiles/autopilot-triage"><img src="https://agentmods.dev/badge/skills/joshukraine/dotfiles/autopilot-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.02063 |
| Opus 5.5 | $0.00018 | $0.00825 |
| Sonnet 5.5 | $0.00009 | $0.00413 |
| Haiku 4.5 | $0.00004 | $0.00206 |
Grade A, and why
autopilot-triage 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 1mo 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autopilot Triage
Vet a pool of open issues against the autonomy rubric and, after your confirmation, tag the ones that qualify with the autopilot-queued label. /autopilot-batch later reads that label and runs the batch. This is the vet half of the triage → run split; the two are decoupled on purpose — triage once (cheap, start-of-day), run the batch whenever and from wherever.
The autopilot-queued label is membership only: it means "vetted and pending," nothing more. Tier is decided at run time by your --merge opt-in, never encoded in it. The build model rides on a separate, pre-existing label (model: fable / model: opus / model: sonnet) that issue triage assigns — this skill reports that label, it does not assign one.
Where this runs
Run from the target application repository — you need the issues and the code, because vetting scope means looking at what a fix would actually touch. Triage is read-only except for the label writes it makes after your confirm.
Arguments
- (no args) — vet all open issues.
[label-or-filter]— narrow the candidate pool, e.g. a phase label orchore/fix. Passed through togh issue list --label.
The autonomy rubric
An issue qualifies for autopilot when all hold:
- Complete spec — clear acceptance criteria; you could hand it off with no back-and-forth.
- Bounded scope — a few files, one subsystem, a known pattern to follow (the positive exemplar: a "localize these hardcoded strings" i18n issue).
- No product / UX / design decision — nothing that needs your judgment about what to build.
- Testable — its resolution can be proven by the suite (or a targeted inline check).
An issue is disqualified when it trips any of /autopilot's own escape-hatch triggers — the same guardrails, applied before the run instead of during it:
- a new DB column / migration, a changed model association, an altered public route, a new dependency, or an event-status-lifecycle change;
- a thin or ambiguous spec, or one that conflicts with the code;
- multiple subsystems, a real design choice, or anything you'd want to review mid-flight.
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.
- 1mo ago First seen · 124 lines · 44 tokens per session scan A 25b8289de0f9
autopilot-triage is a skill published in the GitHub repository joshukraine/dotfiles (429 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 2,063 once invoked, about $0.0002 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-30.
Other skills, from other repositories
mbo-plan
Plan a new objective end-to-end in this repo's docs/mbo Management-By-Objective system — turn a GitHub issue or a gss draft-PR worktree into consistent design/spec/plan artifacts and track it in docs/mbo/index.md. Use this whenever the user wants to START planning or designing a new feature, skill, CLI, or service…
issue-grooming
Use when the user wants to groom, triage, prioritize, or clean up the GitHub issue backlog of a repo: "groom the issues", "triage the backlog", "which issues are already done", "prioritize the open issues", "close stale issues", "label issues 1-5", "refactor old issues to match the repo", or a periodic backlog review…
show-issues-overview
Show a table-formatted overview of the current repository's issues, from GitHub Issues, GitLab Issues, or a TODO.md-like file when the project has neither. Use when the user asks what issues/tasks are open, wants to decide what to work on next, or invokes /show-issues-overview.
sync-labels-from-prs-and-sub-issues
A workflow for calculating area labels from the files changed by pull requests and sub-issues, then synchronizing those labels across related GitHub items. Labels are tags used to group and filter work.
link-this-pr-to-issue
A GitHub procedure for linking a pull request (PR) to an issue, a GitHub task or bug report, by adding a closing phrase such as “Closes #123” to the PR description. Merging the PR can then close the linked issue automatically.
sync-issue-title-and-detail-to-this-pr
A workflow for keeping a pull request's title and summary aligned with its parent GitHub issue. A pull request is a proposed code change, while an issue tracks the work or problem behind it.