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-complete-milestonegit 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-complete-milestone)<a href="https://agentmods.dev/skills/ferroxlabs/ijfw/ijfw-complete-milestone"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-complete-milestone/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-complete-milestone"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-complete-milestone.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 24 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00062 | $0.01530 |
| Opus 5 | $0.00031 | $0.00765 |
| Sonnet 5 | $0.00012 | $0.00306 |
| Haiku 4.5 | $0.00006 | $0.00153 |
Grade A, and why
ijfw-complete-milestone 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 7d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive a completed milestone, capture what shipped, and surface the next milestone. Domain-agnostic -- a milestone may be a software release, a book part, a campaign wave, a design-system tier, or any other top-level project unit defined in .planning/ROADMAP.md.
Inputs
- Milestone identifier (e.g.
1.5.0,part-two,wave-3). If the user did not name one, ask once:Which milestone are we wrapping?Accept any string that appears as a milestone heading in.planning/ROADMAP.md.
Process
-
Verify completion.
- Read
.planning/ROADMAP.md. Find the milestone block for<id>. - List every phase under that milestone. For each phase, check that it is marked complete (e.g.
[x],status: complete,shipped, or has aSUMMARY.mdin.planning/<milestone>/<phase>/). - If any phase is incomplete: surface the gap and ask
Proceed anyway and treat the open phase as deferred? (y / fix first). Do not auto-advance.
- Read
-
Extract learnings (dispatch agent).
- Dispatch
ijfw-extract-learningswith the milestone scope. The agent reads everySUMMARY.md,RETRO.md, and commit message in.planning/<milestone>/**and writes.planning/<milestone>/LEARNINGS.md(decisions, surprises, patterns, lessons). - If the agent is unavailable in this runtime, write a stub
LEARNINGS.mdwith_pending: dispatch ijfw-extract-learnings when available_and surface the gap.
- Dispatch
-
Generate milestone summary (dispatch skill).
- Dispatch
ijfw-milestone-summarywith<id>. The skill writes.planning/<milestone>/SUMMARY.md-- stats, accomplishments, timeline, contributors -- suitable for a release post, book-part wrap, campaign retro, or design-tier handoff. - Paste the summary's first 6 lines in-chat so the user sees what landed.
- Dispatch
-
Confirm with user.
- Show: milestone id, phase count, days elapsed (first → last commit in scope), first line of SUMMARY.md, first 3 LEARNINGS entries.
- Ask:
Archive and seed next milestone? (yes / show full summary / hold). - On
hold: stop. The artifacts remain in place; the user can re-run later.
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.
- 7d ago First seen · 98 lines · 62 tokens per session scan A a3a2cffb47fa
ijfw-complete-milestone is a skill published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 5d ago), licensed MIT. It adds 62 tokens to every session and 1,530 once invoked, about $0.0003 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…
aside-notion
Read this skill when you need to use Notion. Don't have to open a browser tab.
agent-chief-of-staff
Personal communication chief of staff that triages email, Slack, LINE, and Messenger. Classifies messages into 4 tiers (skip/infoonly/meetinginfo/actionrequired), generates draft replies, and enforces post-send follow-through via hooks. Use when managing multi-channel communication workflows.