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 FerroxLabs/ijfw --skill ijfw-shipgit clone --depth 1 https://github.com/FerroxLabs/ijfwWrote 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/ferroxlabs/ijfw/ijfw-ship)<a href="https://agentmods.dev/skills/ferroxlabs/ijfw/ijfw-ship"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-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/ferroxlabs/ijfw/ijfw-ship"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00139 | $0.01864 |
| Opus 5 | $0.00069 | $0.00932 |
| Sonnet 5 | $0.00028 | $0.00373 |
| Haiku 4.5 | $0.00014 | $0.00186 |
Grade A, and why
ijfw-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 4d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IJFW Ship — domain-aware release closer
You are the orchestrator-facing trigger that closes a slice and pushes it into the world. Same closing arc across domains: pre-flight → execute the release → confirm in the wild → update memory. The verb "ship" differs by domain; the discipline doesn't.
This skill is the body for the /ijfw-ship slash command. Both paths land
here.
When to fire
- User explicitly asks: "ship it", "release", "publish", "launch", "deploy", "go live", "wrap this up", "time to ship".
/ijfw-shipslash command is invoked.- ijfw-workflow Deep path enters the Ship gate after Verify.
Domain detection
Detect from project layout + brief language:
| Domain | Signals | Ship verb |
|---|---|---|
| software | package.json / pyproject.toml / Cargo.toml |
tag + publish |
| book / chapter | manuscript/, chapters/, agent / KDP / Substack ref |
format + submit |
| campaign | campaign/, calendar.md, channel language |
schedule + send |
| landing page | next.config.*, astro.config.*, deploy host configs |
deploy + verify |
| design system | tokens/, components/, registry / npm package |
publish + announce |
If the domain is ambiguous, ask one AskUserQuestion: What are we shipping?
with the five options above. Never guess.
Pre-ship checklist (domain-aware)
Software
- CHANGELOG.md updated with what's in this release.
- Test suite green (
npm test/pytest/cargo test) — fresh run, this session, raw output. - Version bumped in
package.json/ equivalent. - Tag drafted (
v<MAJOR>.<MINOR>.<PATCH>); push deferred until push-word. - Rollback plan documented (
npm deprecate/cargo yank/ revert + retag).
Book / chapter
- Manuscript final edit pass done.
- Format pass complete (epub / pdf / docx, depending on channel).
- Front-matter (title page, copyright, dedication, ISBN if owned) present.
- Cover + back-cover copy finalised.
- Target channel decided: Amazon KDP, agent submission, Substack, direct.
- Rollback plan = unpublish window noted (KDP allows ~72h unpublish; agent withdrawal letter ready if submitted).
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.
- 4d ago First seen · 190 lines · 139 tokens per session scan A a2c0b03c9665
ijfw-ship is a skill published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 2d ago), licensed MIT. It adds 139 tokens to every session and 1,864 once invoked, about $0.0007 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-09-05.
Other skills, from other repositories
release-verification
A release-verification checklist for software versions and packages. It covers changelogs, tests, packaging, installation smoke checks, version-control actions, publishing, and checks after release.
audit-release
A pre-release review assistant that checks whether a software package or plugin is ready to publish.
ds-ship
Ship orchestrator — classify the project, pick a mode (improve/release/launch/maintain), delegate only the skills the project's signals justify, consolidate findings, produce an audit report. Use for an end-to-end audit or ship pipeline across multiple skills.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.