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-ui-specgit 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-ui-spec)<a href="https://agentmods.dev/skills/ferroxlabs/ijfw/ijfw-ui-spec"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-ui-spec/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-ui-spec"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-ui-spec.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.00083 | $0.02028 |
| Opus 5.5 | $0.00033 | $0.00811 |
| Sonnet 5.5 | $0.00017 | $0.00406 |
| Haiku 4.5 | $0.00008 | $0.00203 |
Grade A, and why
ijfw-ui-spec 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IJFW UI-Spec -- lock the visual contract before build
Produce .planning/<milestone>/<phase>/UI-SPEC.md as the design contract for
the active slice, then dispatch ijfw-ui-auditor as the final 6-pillar gate
after implementation lands.
Domain-agnostic. Same flow for: a web UI slice ("settings page"), a book chapter layout ("Ch4 spread + typography"), a campaign deck ("launch deck 8 slides"), a brand system ("v2 token refresh"). UI-SPEC.md is the visual counterpart to SPEC.md.
When to fire
- User explicitly asks: "ui spec", "design contract", "ui audit setup",
"lock the design", or invokes
/ijfw-ui-spec. - ijfw-workflow Deep path enters a frontend or visual-artifact build with no UI-SPEC.md present.
- plan-phase is requested for a slice tagged
ui:*orvisual:*and no UI-SPEC.md exists.
Process
1. Locate the active slice
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}"
MOCKUP_DIR="${PHASE_DIR}/mockups"
mkdir -p "$PHASE_DIR" "$MOCKUP_DIR"
If $PHASE is unset and no argument supplied, ASK which slice to spec.
Never guess.
2. Load context
Read in order, skipping any that don't exist:
.ijfw/memory/brief.md-- the original askDESIGN.md-- existing design contract (root).planning/<milestone>/<phase>/SPEC.md-- locked WHAT for this slice.planning/<milestone>/<phase>/CONTEXT.md-- discuss-phase decisions- Any prior
UI-SPEC.mdin earlier slices of this milestone .planning/PROJECT.md-- non-negotiables
Extract: brand direction, declared surfaces, prior token decisions, the critical surfaces that must visualise.
3. Trigger ijfw-design if no design contract exists
If neither DESIGN.md nor a prior UI-SPEC.md lives in the repo, defer
to the ijfw-design skill to pick a direction (brand / template / blank
slate) and persist DESIGN.md. Resume from Step 4 once design pass landed.
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 · 201 lines · 83 tokens per session scan A 096d1ae78edf
ijfw-ui-spec is a skill published in the GitHub repository FerroxLabs/ijfw (214 stars, last pushed 6d ago), licensed MIT. It adds 83 tokens to every session and 2,028 once invoked, about $0.0003 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
ui-designer
Designs and builds interface work on top of the design system the repo already has: layout, spacing, hierarchy, interaction states, and accessible defaults, with creativity calibrated to the surface instead of an unrequested redesign. Use when asked for a new screen, a redesign, empty, loading, and error states, or to…
web-stylebook-design
Use BEFORE building, auditing, improving, or redesigning any frontend UI (a page, screen, component, dashboard, form, checkout, chat, or developer console). Confirms audit coverage and change depth, then calls the Web Stylebook MCP to evaluate visual design, user-facing copy and information structure, behavior…
lagann
Design director for web and app interfaces. Use it FIRST, before other design skills, whenever the user wants to create, redesign, restyle, polish, fix, animate or review anything visual in a UI, even a small CSS tweak, and even without saying "design": landing pages, dashboards, app screens, "make it look better"…
ui
Build and refine user interfaces with Tailwind CSS. Use when the user asks to build, design, style, or refine web UI — landing pages, dashboards, marketing sections, forms, buttons, cards, pricing tables, hero sections, testimonials, or Tailwind markup cleanup. Generates multiple design variations on exploratory…
frontend-design-direction
A set of design guidelines for building web pages, apps, dashboards, and other user interfaces with a clear visual direction. It addresses layout, typography, color, motion, hierarchy, and interaction choices.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".