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 jkomyno/.dotfiles --skill ship-itgit clone --depth 1 https://github.com/jkomyno/.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/jkomyno/.dotfiles/ship-it)<a href="https://agentmods.dev/skills/jkomyno/.dotfiles/ship-it"><img src="https://agentmods.dev/badge/skills/jkomyno/.dotfiles/ship-it/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/jkomyno/.dotfiles/ship-it"><img src="https://agentmods.dev/badge/skills/jkomyno/.dotfiles/ship-it.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.00039 | $0.00438 |
| Opus 5 | $0.00019 | $0.00219 |
| Sonnet 5 | $0.00008 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
ship-it 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 10d 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
Ship It
Close the gap between implementation-complete and actually shipped. Keep local proof, hosted CI, approval, merge, tagging, and publication as separate states.
Inventory
Gather current evidence in this order:
- Working tree, current branch, recent commits, upstream, and branches ahead of the default branch.
- Open PRs and the exact head, base, review, merge, and check state of any release-shaped PR.
- Changeset or release-plan state when the repository uses one.
- Source version, package registry versions and dist-tags, Git tags, and hosted release artifacts.
- Required CI state and any approval or environment gates.
- Repository visibility or publication prerequisites when relevant.
Classify
Separate every remaining step into:
- Authorized and reversible: scoped source fixes, changelog updates, version changes, release notes, and feature-branch or PR work allowed by the user's request and repository policy.
- Needs explicit authority: default-branch pushes, merges, first publication, stable-channel promotion, visibility changes, deletions, or any other consequential public action not already requested.
Do not label an action safe merely because a CLI supports it. Consider its external effect and the authorization already granted in the conversation.
Execute And Verify
Perform every authorized step, one reviewable concern at a time. Follow the global Git and PR policy for initial branch publication and subsequent pushes. After each external action, re-read the remote state and verify the resulting tag, artifact, version, checksum, or dist-tag at the boundary users consume.
Stop at the first step that needs new authority and provide the exact command or UI action the user must approve.
Report
State what shipped, distinguish it from what merely passed locally, list the
remaining human gates, and end with the standard What's next: handoff line.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 53 lines · 39 tokens per session scan A 41b2e27fcd4f
ship-it is a skill published in the GitHub repository jkomyno/.dotfiles (5 stars, last pushed 5d ago), licensed MIT. It adds 39 tokens to every session and 438 once invoked, about $0.0002 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-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.