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-milestone-summarygit 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-milestone-summary)<a href="https://agentmods.dev/skills/ferroxlabs/ijfw/ijfw-milestone-summary"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-milestone-summary/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-milestone-summary"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-milestone-summary.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.00079 | $0.01517 |
| Opus 5 | $0.00039 | $0.00758 |
| Sonnet 5 | $0.00016 | $0.00303 |
| Haiku 4.5 | $0.00008 | $0.00152 |
Grade A, and why
ijfw-milestone-summary 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 5d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Produce an onboarding doc for someone joining mid-stream. Output: .planning/<milestone>/SUMMARY.md.
Domain-agnostic: "what shipped" means chapters drafted for a book, launches that landed for a campaign, features released for software, episodes recorded for a podcast. Adapt the noun to the project type.
Step 1 -- Resolve milestone
Argument is the milestone slug (e.g. 1.5.0, q2-launch, book-draft-2). If absent:
- Read
.ijfw/state/workflow.json-- use the current milestone field. - Else read
.planning/ROADMAP.md-- pick the active milestone. - Else list directories under
.planning/and ask which one.
Set MS="<resolved-slug>". Set OUT=".planning/${MS}/SUMMARY.md".
Step 2 -- Inventory artifacts
Read whatever exists, skip whatever doesn't. Missing files are normal -- the doc adapts.
.planning/ROADMAP.md-- scope, dates, status of each item..planning/${MS}/SUMMARY.md-- prior version (overwrite guard, see Step 6)..planning/${MS}/**/SUMMARY.md-- per-item outcomes..planning/${MS}/**/LEARNINGS.md-- per-item decisions (written by ijfw-extract-learnings / C06)..planning/${MS}/**/VERIFICATION.md-- gaps, deferred items.CHANGELOG.md-- the${MS}entry if present.- Git log for the milestone tag range:
- If
v${MS}tag exists:git log --oneline v${MS}andgit log v${MS}~1..v${MS} --stat. - Else:
git log --since="<earliest .planning/${MS}/ commit date>" --oneline. - Else: skip git stats.
- If
Step 3 -- Synthesize
Compose the doc with these six sections in this order. Plain English. No jargon a new contributor wouldn't know.
What shipped
One paragraph, 3-5 sentences. Lead with the user-visible outcome ("v1.5.0 shipped runtime honesty + pluggability completion -- the workflow now self-audits, dispatches parallel subagents, and runs cross-model critique unattended"). Avoid implementation detail. Adapt the noun:
- software: features shipped
- book: chapters drafted, edits landed
- campaign: launches that landed, channels lit up
- podcast: episodes recorded and published
- research: papers drafted, experiments concluded
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.
- 5d ago First seen · 123 lines · 79 tokens per session scan A 8408be63c2c6
ijfw-milestone-summary is a skill published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 3d ago), licensed MIT. It adds 79 tokens to every session and 1,517 once invoked, about $0.0004 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
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.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
change-manager
name: change-manager description: Used when the user adds a feature or incrementally changes an existing project that already has Product-Spec.md. Runs the changes/ workflow (propose, apply, verify, archive), aligned with OpenSpec-style SDD while delegating implementation to dev-planner and dev-builder. version: 1.1.0…
product-strategy
A product-planning guide for evaluating requirements, users, scope, priorities, roadmaps, and success measures. It ties proposals to user problems, business value, boundaries, and signals that can be checked.
slice-closure
Decide whether the current slice is ready to close, distinguishing slice completion from full task completion, then persist the result in slice notes and TASKSTATE.md as explicit reviewable closure notes. For single-slice tasks may route directly to delivery. Returns no-op when slice memory would not materially…