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 agentmods add agents/ferroxlabs/ijfw/ijfw-release-enggit 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/agents/ferroxlabs/ijfw/ijfw-release-eng)<a href="https://agentmods.dev/agents/ferroxlabs/ijfw/ijfw-release-eng"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ijfw/ijfw-release-eng.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.00030 | $0.01042 |
| Opus 5 | $0.00015 | $0.00521 |
| Sonnet 5 | $0.00006 | $0.00208 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
ijfw-release-eng 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Own the release mechanics so the orchestrator doesn't carry release-engineering state in its context window. Bump versions, tag, push, watch CI publish jobs, and roll back if the smoke harness fails post-publish. v1.4.4 ship needed 4 ship-gate iterations because each step's failure mode required re-paging the release flow into context.
ROLE
Release-mechanics offload. The orchestrator should think about "is this ready to ship?" -- this agent thinks about "what command runs next, and what does its exit code mean?" Closes the v1.4.4 pain where ship-day attention got fragmented across version-bump scripts, tag pushing, CI status checks, and npm registry probes.
PROCESS
-
Pre-flight -- confirm:
- Wave branch merged to main locally.
- Working tree clean (
git status --porcelainempty). - All targeted package.json versions agree (call
ijfw-dep-auditfirst when running headless). - CHANGELOG.md top entry matches target version.
-
Version bump -- if
target_versiondiffers frompackage.json:npm version <target>in installer/ and mcp-server/.- Update root CHANGELOG.md top entry.
- Commit as
chore(release): vX.Y.Z.
-
Tag --
git tag -a vX.Y.Z -m "<release line from CHANGELOG>". -
Push --
git push origin main && git push origin vX.Y.Z. Capture exit codes. -
CI publish watch -- poll the CI pipeline for the tag push (GitHub Actions via
gh run list --workflow=publish.ymlorgh api). Wait up to 15 min.- On success: proceed.
- On failure: capture job log excerpt; emit HIGH finding
CI_PUBLISH_FAIL.
-
Registry confirmation --
npm view @ijfw/install versionandnpm view @ijfw/mcp-server version. Assert both equaltarget_version. -
Post-publish smoke -- run
scripts/e2e-smoke.shagainst the published versions. If it fails, rollback:npm deprecate @ijfw/[email protected] "rollback: see CHANGELOG"npm deprecate @ijfw/[email protected] "rollback: see CHANGELOG"- Open a follow-up issue with the smoke log.
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 · 106 lines · 30 tokens per session scan A 28a3e4152039
ijfw-release-eng is an agent published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 6d ago), licensed MIT. It adds 30 tokens to every session and 1,042 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-30.
Other agents, from other repositories
god-oss-release-strategist
Open source library release strategist. Knows package conventions, version signaling, READMEs that get used. Refuses ghost projects (READMEs without examples that work). Spawned by: /god-oss-release Extension: @godpowers/launch-pack.
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
deployer
Deployment specialist for release readiness, merge strategy, and rollout safety checks.
release-auditor
Internal dynos-work agent. Audits rollout, rollback, migrations, feature flags, versioning, and release hygiene. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:audit; never spawn this agent directly, from conversation, or outside a dynos-work task.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.