Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tonykipkemboi/skill-foundrynpx agentmods add skills/tonykipkemboi/skill-foundry/ship-pluginWrote 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/tonykipkemboi/skill-foundry/ship-plugin)<a href="https://agentmods.dev/skills/tonykipkemboi/skill-foundry/ship-plugin"><img src="https://agentmods.dev/badge/skills/tonykipkemboi/skill-foundry/ship-plugin.svg" alt="Measured on agentmods" 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.00046 | $0.03511 |
| Opus 5 | $0.00023 | $0.01755 |
| Sonnet 5 | $0.00009 | $0.00702 |
| Haiku 4.5 | $0.00005 | $0.00351 |
Grade A, and why
ship-plugin 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 6d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Plugin
Drive the full pipeline: take loose skill files (SKILL.md, .skill archives, reference
docs), package them into this plugin, run all policy checks locally, and open a PR to
the department's GitHub repo. CI is the authoritative gate, so never push to main.
Optimize for accuracy over speed: each step below guards against a known failure mode. Do them all, in order, even when the change looks trivial.
Two rules before you touch anything (read first)
These apply no matter which assistant runs this (Claude Code, Codex, etc.):
-
Work on a branch, never on
main. Before any commit, rungit rev-parse --abbrev-ref HEAD. If it returnsmain, create a feature branch first (git checkout -b add-<skill-name>). Do not commit, edit-then-commit, or push onmainat any point. Every change ships through a branch and a PR. -
When you need a decision, ask. Don't guess. Whenever the next step depends on a choice only the user can make, STOP and ask using the AskUserQuestion tool (or your platform's equivalent interactive prompt) before proceeding. Examples that require asking: new plugin vs. add-to-existing; the plugin name/slug; which existing plugin to target; what the skill should be named if it's ambiguous; whether to include a skill that won't work in the target runtime; the semver bump level if unclear. Never assume a consequential answer.
Make each question easy to answer well. Use the normal terms (plugin, skill), which they know, but with every question briefly say why you're asking and what the choice leads to, and give an example of a good answer. When you can discover the options yourself, present them as concrete choices instead of an open question: for example, run
gh repo list YOUR-ORGor read the existing plugins and offer them as a pick-list for "which plugin should this join?". Invite the user to ask back if anything is unclear before they answer.
Step 0: Preflight (audit the repo state before planning anything)
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.
- 6d ago First seen · 273 lines · 46 tokens per session scan A 4ad04ae76a91
ship-plugin is a skill published in the GitHub repository tonykipkemboi/skill-foundry (2 stars, last pushed 20d ago), licensed MIT. It adds 46 tokens to every session and 3,511 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
changelog-rules
Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.
create-changelog
Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".
update-changelog
Update the Unreleased section of CHANGELOG.md based on current changes. No-op if CHANGELOG.md does not exist. Use when the user asks to "update changelog", "add to changelog", "update the changelog", "changelog entry", "add changelog entry", or "log this change".
changelog
Use when writing a changelog or release notes. Covers what belongs in one, writing for users rather than for git, semantic versioning, and documenting breaking changes so nobody is surprised.
git-workflow
Use for branching, committing, history repair, and release hygiene. Covers atomic commits, rebase versus merge, bisect, reflog recovery, and undoing mistakes safely.
app-release
Automates the release process for Skill Lake app, including version bumping, building, packaging, and publishing to GitHub and Homebrew.