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 chipi/agentic-ai-homelab --skill shipgit clone --depth 1 https://github.com/chipi/agentic-ai-homelabWrote 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/chipi/agentic-ai-homelab/ship)<a href="https://agentmods.dev/skills/chipi/agentic-ai-homelab/ship"><img src="https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/ship/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/chipi/agentic-ai-homelab/ship"><img src="https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/ship.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.00081 | $0.00540 |
| Opus 5 | $0.00041 | $0.00270 |
| Sonnet 5 | $0.00016 | $0.00108 |
| Haiku 4.5 | $0.00008 | $0.00054 |
Grade A, and why
ship 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 9d 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
The disciplined path from "work is done" to "pushed" — so nothing lands unrebased, unvalidated, or unapproved. The push is shared-state and gated on explicit approval, every time.
Steps
- Branch check. Never push the trunk directly. If on
main, stop — branch first. Confirm the feature branch and what it's ahead of. - Secrets. Run the
secrets-scanskill over the diff. A hit blocks the push. - Rebase onto trunk.
git fetch origin main && git rebase origin/main. Resolve conflicts; never leave a merge commit on a feature branch. Do this every push, not just the first. - Run the right gates — not the heaviest. Run the validation that actually
covers the change (
docs-preflightfor docs, the relevantmaketarget, the specific test). Reproduce green locally; don't push-and-let-CI-find-it. End each gate with an unambiguous PASS/FAIL. - Show what ships.
git status+git --no-pager diff origin/main...HEAD --stat- the commit log about to land. Summarize it.
- Get explicit approval. Wait for "push" / "ship it" / "go". Approval for a previous push does NOT carry to this one.
- Push.
git push --force-with-leaseif the branch is already on the remote (post-rebase), elsegit push -u origin <branch>. PRs default to ready, not draft, unless asked otherwise.
Non-negotiables this enforces
- Never push without explicit approval (rule #1) — per push, not per session.
- Always rebase onto the trunk before pushing (rule #2) —
--force-with-lease. - Red required CI = fix until green (rule #3).
- Green local, then push (rule #11) — reproduce failures locally first.
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.
- 9d ago First seen · 38 lines · 81 tokens per session scan A 62d5320c0457
ship is a skill published in the GitHub repository chipi/agentic-ai-homelab (2 stars, last pushed 2d ago), licensed MIT. It adds 81 tokens to every session and 540 once invoked, about $0.0004 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
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
changelog-scan
Scan merged PRs and commits since a given reference, extract titles, labels, types, and signals. Produces structured input for release notes drafting.
draft-release-notes
Turn changelog-scan output into polished, categorized release notes draft. Propose only.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
release-notes
Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.
release-sidecar
Release new versions of sidecar. Covers version tagging with semver, td dependency updates, go.mod validation, CHANGELOG updates, GoReleaser automation, Homebrew tap updates, and verification steps. Use when preparing or executing a release.