Borrowing it
Nothing to install: this file belongs to eduardoarantes/agentenv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/eduardoarantes/agentenv/main/.claude/skills/ship-changes/SKILL.mdgit clone --depth 1 https://github.com/eduardoarantes/agentenvWrote 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/eduardoarantes/agentenv/ship-changes)<a href="https://agentmods.dev/skills/eduardoarantes/agentenv/ship-changes"><img src="https://agentmods.dev/badge/skills/eduardoarantes/agentenv/ship-changes/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/eduardoarantes/agentenv/ship-changes"><img src="https://agentmods.dev/badge/skills/eduardoarantes/agentenv/ship-changes.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.00061 | $0.01611 |
| Opus 5.5 | $0.00024 | $0.00644 |
| Sonnet 5.5 | $0.00012 | $0.00322 |
| Haiku 4.5 | $0.00006 | $0.00161 |
Grade A, and why
ship-changes 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship changes
Wraps a tested working tree into a published PR. Three phases — audit, commit + push, open PR. Each phase has hard checks; if any fail, stop and report instead of pushing forward.
Phase 1 — audit the diff
Inspect what's about to ship and decide whether documentation needs to move with it.
-
Run the inspection commands in parallel (single tool message, multiple Bash calls):
git status— uncommitted filesgit diff --stat— scope at a glancegit diff(andgit diff --cachedif there's staged content) — actual changesgit log -10 --oneline— recent commit-message style for this repogit branch --show-current— branch you're shipping from
-
Refuse to proceed if:
- Working tree is clean (nothing to ship — say so and stop).
- Files that look sensitive are staged (
.env*,*credentials*,*.pem,*.key, anything matching**/secrets/**). Surface the path and ask the user before continuing.
-
Documentation audit — walk the diff for these signals and report each finding:
Signal in diff Doc that probably needs updating Public API change in crates/*/src/lib.rsor anypub fn/pub structdoc-comments on the changed item; mentions in docs/New CLI subcommand / flag in crates/agentenv-cli/src/main.rsREADME.mdexamples;docs/runbooksNew config field, target name, or capability in crates/agentenv-core/src/config.rsschemas/agentrc.schema.json,.agentrc.example.yaml,CLAUDE.md,docs/platform-standards.mdNew / changed writer or reader path docs/platform-standards.mdper-tool tables,docs/HOOKS.mdNew module under crates/agentenv-core/src/CLAUDE.mddevelopment-areas sectionTest fixtures touching .agentrc.yamlshape.agentrc.example.yamlCargo.tomldep addednothing required, but flag the new dep in the PR body For each finding, check whether the doc already reflects it — grep the doc for the changed identifier / config key. If it does, note "doc already covers it" and move on. If it doesn't, stop and tell the user before committing. List the missing doc updates as a punch list; let the user decide whether to update them now, defer, or proceed without.
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 · 137 lines · 61 tokens per session scan A d7f5ce4e1ad4
ship-changes is a skill published in the GitHub repository eduardoarantes/agentenv (5 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 1,611 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
apply
Apply a prior /repo-fleet-hygiene:audit action-plan JSON behind one fleet confirmation: default dry-run re-derives branch/worktree tips and prints the ordered batch; --apply mutates only after interactive confirmation or --yes. Owns batched merged-local-branch deletion with fail-closed OID refresh; cleans…
git-workflow
Git workflow and conventional commits. Use when working with git, branches, commits, pull requests, code review, or version control strategy.
diff-review
Render the patch-edit run's accumulated changes as a reviewable diff, surface it through a GenUI choice surface, and persist the user's accept / reject decision into the artifact manifest.
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
hunk-launch-video
Produces Hunk videos by driving the real TUI headlessly in a PTY, compositing captioned 1080p frames in Chromium, and encoding with ffmpeg. Use for feature demos, workflow explainers, announcements, launch videos, and full-release roundups.
hunk-release
Prepares, publishes, verifies, and curates Hunk releases. Use for release metadata, benchmarks, tags, publishing, release videos, backports, or recovery.