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.
git clone --depth 1 https://github.com/vignesh2027/AI-AGENT-SKILLSWrote 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/commands/vignesh2027/ai-agent-skills/ship)<a href="https://agentmods.dev/commands/vignesh2027/ai-agent-skills/ship"><img src="https://agentmods.dev/badge/commands/vignesh2027/ai-agent-skills/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/commands/vignesh2027/ai-agent-skills/ship"><img src="https://agentmods.dev/badge/commands/vignesh2027/ai-agent-skills/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.00000 | $0.00165 |
| Opus 5 | $0.00000 | $0.00082 |
| Sonnet 5 | $0.00000 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00016 |
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 8d 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
Load skills/deployment-strategy/SKILL.md, skills/git-workflow-and-versioning/SKILL.md, and skills/documentation-and-adrs/SKILL.md.
Prepare for deployment. Before proceeding, verify:
- Rollback procedure — Write it now. How do you revert if this fails?
- Deployment stages — Define: which stages, bake time at each
- Success criteria — What metrics must hold for this to be "successful"?
- Database migrations — Are they backward compatible?
- Feature flags — Is new functionality behind a flag?
- Documentation — Is it updated?
- Monitoring — Are alerts in place for the new behavior?
Do not deploy until the rollback procedure is written and success criteria are defined.
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.
- 8d ago First seen · 14 lines · 0 tokens per session scan A 8f6d63844507
ship is a command published in the GitHub repository vignesh2027/AI-AGENT-SKILLS (2 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 165 tokens. 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 commands, from other repositories
iterate
Iteration delivery — delivery check + archive + commit & tag + bump version.
ship
Prepare the current branch for review and deployment.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
release-tag
Create and push a version tag after a release PR has been merged.
release
Generate changelog, bump version, and create git tag.
create-release-note.en
Generate release notes from PRs and commits.