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 mattgierhart/PRD-driven-context-engineering --skill prd-v04-screen-flow-definitiongit clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineeringWrote 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/mattgierhart/prd-driven-context-engineering/prd-v04-screen-flow-definition)<a href="https://agentmods.dev/skills/mattgierhart/prd-driven-context-engineering/prd-v04-screen-flow-definition"><img src="https://agentmods.dev/badge/skills/mattgierhart/prd-driven-context-engineering/prd-v04-screen-flow-definition/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/mattgierhart/prd-driven-context-engineering/prd-v04-screen-flow-definition"><img src="https://agentmods.dev/badge/skills/mattgierhart/prd-driven-context-engineering/prd-v04-screen-flow-definition.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.00134 | $0.02791 |
| Opus 5 | $0.00067 | $0.01396 |
| Sonnet 5 | $0.00027 | $0.00558 |
| Haiku 4.5 | $0.00013 | $0.00279 |
Grade A, and why
prd-v04-screen-flow-definition 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 10d 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Screen Flow Definition
Position in workflow: v0.4 User Journey Mapping → v0.4 Screen Flow Definition → v0.5 Red Team Review
Screens are where journeys become tangible. This skill transforms user journeys into a screen inventory with navigation paths and feature mappings.
Consumes
This skill requires prior work from v0.3-v0.4:
- UJ-* user journey entries (from v0.4 User Journey Mapping) — Journey steps become screens; each step asks "What screen enables this action?"
- FEA-* feature entries (from v0.3 Features Value Planning) — Features map to screens showing which features appear on which screens
- PER-* persona entries (from v0.4 Persona Definition) — Persona context (technical level, role) shapes screen design choices and complexity
- MVP-SCOPE artifact (from v0.3 Features Value Planning) — Explicit feature boundary; screens must render only MVP-scoped features, backlog features deferred
- BR-* business rules (from v0.3 Commercial Model) — Constraints affecting screen layout (pricing tier rules affect which settings appear, role-based visibility, data refresh rates, etc.)
This skill assumes v0.4 User Journey Mapping is complete.
Produces
This skill creates/updates:
- SCR-* entries (screens, confidence 2-3/5) — Screen inventory with journey/feature/persona mappings showing purpose, actions, navigation, and constraints
- DES-* entries (design system components, confidence 2-3/5) — Reusable UI elements and patterns identified across screens
- Feature-to-Screen matrix — Validation artifact showing every FEA- and every UJ- step mapped to SCR-
- Screen count and complexity assessment — Critical for v0.5 technical stack selection (number of screens informs frontend framework needs)
All SCR- entries should include:
confidence: 2-3/5(based on journey validation and feature implementation status)- Evidence source citations (UJ-ID, FEA-ID, PER-ID references)
- Forward target: "Would move to 4/5 if validated in wireframe review or prototype testing"
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 294 lines · 134 tokens per session scan A 023b4fe08a07
prd-v04-screen-flow-definition is a skill published in the GitHub repository mattgierhart/PRD-driven-context-engineering (182 stars, last pushed 10d ago), licensed MIT. It adds 134 tokens to every session and 2,791 once invoked, about $0.0007 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-08-30.
Other skills, from other repositories
loft
Loft the shape before cutting steel — answer a design question that prose cannot settle by building a throwaway artifact: a pure logic module in a clickable shell, or structurally different UI variants behind one route. The captain reacts to the artifact; the answer folds into the decision; the artifact never docks.…
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
latex-posters
Use when creating or revising LaTeX research posters with beamerposter, tikzposter, or baposter, including poster layout, typography, color, print sizing, figure placement, QR codes, compilation, and print-ready PDF checks.
infographics
Create professional infographics using Nano Banana Pro AI with smart iterative refinement. Uses Gemini 3 Pro for quality review. Integrates research-lookup and web search for accurate data. Supports 10 infographic types, 8 industry styles, and colorblind-safe palettes.
figma-implement-design
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a…
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.