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-spec-phasegit 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-spec-phase)<a href="https://agentmods.dev/skills/ferroxlabs/ijfw/ijfw-spec-phase"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-spec-phase/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-spec-phase"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-spec-phase.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.00054 | $0.01285 |
| Opus 5.5 | $0.00022 | $0.00514 |
| Sonnet 5.5 | $0.00011 | $0.00257 |
| Haiku 4.5 | $0.00005 | $0.00128 |
Grade A, and why
ijfw-spec-phase 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 1mo 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IJFW Spec-Phase -- lock WHAT before HOW
You are the orchestrator-facing trigger that produces
.planning/<milestone>/<phase>/SPEC.md for the active phase. SPEC.md captures
falsifiable acceptance criteria, explicit in-scope / out-of-scope boundaries,
and dependencies -- BEFORE plan-phase touches HOW to implement.
Domain-agnostic. Same flow for: software slice ("user auth"), book chapter ("Ch4 scope, POV lock, must-cover beats"), campaign slice ("launch week 1 channel mix"), research milestone ("literature review boundaries").
When to fire
- User explicitly asks: "spec this", "scope this", "lock requirements".
- plan-phase / execute-phase is requested but no SPEC.md exists for the
active slice under
.planning/<milestone>/<phase>/. - ijfw-workflow Deep path enters the Plan gate with unclear requirements.
Process
1. Locate the active phase
MILESTONE=$(cat .ijfw/state/active-milestone 2>/dev/null \
|| ls -1 .planning/ | grep -E '^[0-9]' | tail -1)
PHASE=$(cat .ijfw/state/active-phase 2>/dev/null || echo "$1")
PHASE_DIR=".planning/${MILESTONE}/${PHASE}"
mkdir -p "$PHASE_DIR"
If $PHASE is unset and not supplied as argument, ASK the user which phase
to spec. Never guess.
2. Load context
Read in order, skipping any that don't exist:
.ijfw/memory/brief.md-- the original ask.planning/ROADMAP.md-- where this phase sits.planning/<milestone>/ROADMAP.md-- milestone-scoped roadmap- Any prior
SPEC.md/CONTEXT.mdfrom earlier phases in this milestone .planning/PROJECT.md-- non-negotiables
Extract: phase goal, declared boundaries, prior decisions that flow forward.
3. Identify ambiguities (gray areas)
For the phase, list:
- What's clear -- requirements with one obvious interpretation.
- What's gray -- decisions that could go multiple ways and would change the result. Each gray area is a single sentence.
- What's decided -- already locked in a prior phase's CONTEXT.md or SPEC.md.
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.
- 1mo ago First seen · 153 lines · 54 tokens per session scan A e455cf7b38bf
ijfw-spec-phase is a skill published in the GitHub repository FerroxLabs/ijfw (214 stars, last pushed 5d ago), licensed MIT. It adds 54 tokens to every session and 1,285 once invoked, about $0.0002 per session on Opus 5.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
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
subagent-driven-development
A development workflow in which a fresh coding agent implements each independent task, another review checks that task, and a final review examines the complete set of changes.
adr
Create and manage Architecture Decision Records. Documents significant technical decisions with context, alternatives, and consequences. Also supports evaluate (assess proposals) and design (system design) modes.
deploy-checklist
Pre-deployment verification checklist. Generates customized checklists based on tech-stack with rollback triggers. Auto-invoked by /draft:upload.