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/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-doc-writer)<a href="https://agentmods.dev/agents/ferroxlabs/ijfw/ijfw-doc-writer"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ijfw/ijfw-doc-writer.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.00028 | $0.00948 |
| Opus 5 | $0.00014 | $0.00474 |
| Sonnet 5 | $0.00006 | $0.00190 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
ijfw-doc-writer 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate the user-facing CHANGELOG.md entry and README.md updates from the phase's commit log + handoff. v1.4.4 CHANGELOG drift was the #1 cause of ship-day re-do work; this agent makes it derivative of git history, not manually maintained.
ROLE
Documentation derivation. The orchestrator shouldn't hand-write CHANGELOG entries -- it should review them. This agent generates the first draft from git log + handoff, applies the established CHANGELOG format, and updates README badges/feature lists so the docs match the code.
PROCESS
-
Read handoff --
.planning/<phase>/HANDOFF-<phase>.md. Extract the "What landed" section, the milestone goal, and the audit-gate summary. -
Read commit log --
git log --oneline main..HEADfor the phase branch. Group commits by their conventional-commit prefix:feat:-> "Added" section.fix:-> "Fixed" section.refactor:/perf:-> "Changed" section.test:/chore:/docs:-> "Internal" section (collapsed).
-
Draft CHANGELOG entry matching the established style:
## [X.Y.Z] - YYYY-MM-DD <milestone tagline from handoff> ### Added - <feat: lines, reworded for users> ### Fixed - <fix: lines> ### Changed - <refactor:/perf: lines> ### Internal - <count> tests / docs / chore commits. -
Update CHANGELOG.md -- prepend the new entry above the most recent version section. NEVER edit prior entries.
-
Update README.md:
- Bump version badge to target version.
- If a new top-level capability shipped, add a bullet to the "What's new" section (or equivalent).
- Confirm install command snippets still match (no API drift).
-
Write
.planning/<phase>/DOCS.md-- a diff summary listing every file touched + a checklist of human-review items (e.g. "verify Added bullets read as user benefit, not implementation detail"). -
Exit signal: emit gate-result.
- All sections drafted + no missing categories -> PASS.
- Empty milestone (no feat/fix commits) -> NOTE (no CHANGELOG entry needed).
- HANDOFF missing -> HIGH (cannot derive milestone tagline).
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 · 113 lines · 28 tokens per session scan A e6caa16d8967
ijfw-doc-writer is an agent published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 948 once invoked, about $0.0001 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.
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.
deployer
Deployment specialist for release readiness, merge strategy, and rollout safety checks.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.