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 a1f/agent-templates --skill shippedgit clone --depth 1 https://github.com/a1f/agent-templatesWrote 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/a1f/agent-templates/shipped)<a href="https://agentmods.dev/skills/a1f/agent-templates/shipped"><img src="https://agentmods.dev/badge/skills/a1f/agent-templates/shipped/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/a1f/agent-templates/shipped"><img src="https://agentmods.dev/badge/skills/a1f/agent-templates/shipped.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.00056 | $0.03328 |
| Opus 5.5 | $0.00022 | $0.01331 |
| Sonnet 5.5 | $0.00011 | $0.00666 |
| Haiku 4.5 | $0.00006 | $0.00333 |
Grade A, and why
shipped 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 2mo 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shipped
Say it after PRs land; the records catch up. Bookkeeping only — ticks and links:
never merges, never authors prose, never edits the plan (re-planning is
/course-correct's job). Idempotent: a re-run changes nothing, and whatever a prior
run missed is booked next time.
/shipped [--issue=N] [--pr=N]
1. Find the records (plan issue + its artifact)
2. Compare the plan to GitHub (merged but unbooked)
├─ issue lane 3. Tick the issue rows → 5. Tick cross-referenced issues
└─ artifact lane 4. Tick the artifact
join pin the artifact marker, report
No approval gates — never preview or confirm an edit; invoking the skill is the
permission. --pr (or the branch you're on) only seeds discovery — every run still
reconciles all merged-but-unbooked rows.
Phase 1 — Find the records
The plan issue, in order:
--issue=N.- The issue the anchor PR references —
--pr=N, else the current branch's PR or the one just discussed; read its body for the issue link (several plan-issue links count as several candidates). - The conversation — the last
PRD published: ... (issue #N)line. - A repo scan — issues (open, else recently closed) whose body carries a
## PR breakdownsection or a table whose rows describe one PR each.
Never pause to confirm a detection — verify it instead, pulling Phase 2's PR listing
forward: at least one row records or matches a PR of this repo. A plan recording no PR
at all yet qualifies only through steps 1–2, where the user or a PR pointed at it. A failed check on an auto-detected issue
(steps 2–4) falls through to the next step; an explicit --issue or --pr that fails
to resolve — or whose issue fails the check — stops the run and reports, never
falling through past the user's word. More than one issue qualifies, or all four
steps come up dry → ask; headless (no interactive user to ask, e.g. a scheduled run),
stop and report with nothing written.
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.
- 2mo ago First seen · 230 lines · 56 tokens per session scan A 28d68acc7de1
shipped is a skill published in the GitHub repository a1f/agent-templates (2 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 3,328 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-31.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…