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-plangit 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-plan)<a href="https://agentmods.dev/skills/ferroxlabs/ijfw/ijfw-plan"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-plan.svg" alt="Measured on agentmods" 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.00095 | $0.02355 |
| Opus 5 | $0.00048 | $0.01177 |
| Sonnet 5 | $0.00019 | $0.00471 |
| Haiku 4.5 | $0.00010 | $0.00235 |
Grade A, and why
ijfw-plan 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 3d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IJFW Plan — domain-agnostic plan authoring
You are the orchestrator-facing trigger that turns a brief (and optionally a SPEC.md / research notes) into an executable PLAN.md. Plan output is the same shape across domains: software slice, book chapter, marketing campaign, design system release, research milestone. The deliverables differ; the structure doesn't.
This skill is the body for the /ijfw-plan slash command. Both paths land
here. Slash invocation may pass [brief description] as $1.
When to fire
- User explicitly asks: "plan this", "plan it", "make a plan", "let's plan", "draft a plan", "break this down".
/ijfw-planslash command is invoked.- ijfw-workflow Deep path enters the Plan gate after Discovery + Research.
- ijfw-spec-phase has emitted SPEC.md and the user wants HOW next.
If .ijfw/memory/brief.md is missing AND no SPEC.md exists for the active
slice, ask one clarifying question first: What are we planning? (one sentence). Never guess.
Inputs (read in order, skip missing)
.ijfw/memory/brief.md— original ask + success criteria..ijfw/memory/research.md— anything Discovery / Research surfaced..planning/<milestone>/<phase>/SPEC.md— locked acceptance criteria..planning/<milestone>/<phase>/CONTEXT.md— decisions resolved in discuss..planning/ROADMAP.md— where this slice sits in the bigger arc..planning/PROJECT.md— non-negotiables.
Detect domain from brief language and project layout:
- Software:
package.json,pyproject.toml,Cargo.toml, source dirs. - Book / chapter:
manuscript/,chapters/,outline.md, prose-heavy brief. - Campaign / launch:
campaign/,assets/, calendar / channel language. - Design system:
tokens/,components/, design-ops language. - Research:
notes/,papers/, "review the literature" framing.
Domain choice changes vocabulary, NOT the output shape.
Output location
If a phase is active (.ijfw/state/active-milestone + .ijfw/state/active-phase
both exist), write to .planning/<milestone>/<phase>/PLAN.md and also mirror
the task list to .ijfw/memory/plan.md for the runtime gate to read.
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.
- 3d ago First seen · 220 lines · 95 tokens per session scan A 2d74a2545a7e
ijfw-plan is a skill published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed yesterday), licensed MIT. It adds 95 tokens to every session and 2,355 once invoked, about $0.0005 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…