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 paruff/uFawkesAI --skill value-stream-mappinggit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/value-stream-mapping)<a href="https://agentmods.dev/skills/paruff/ufawkesai/value-stream-mapping"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/value-stream-mapping/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/paruff/ufawkesai/value-stream-mapping"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/value-stream-mapping.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00069 | $0.01839 |
| Opus 5 | $0.00034 | $0.00920 |
| Sonnet 5 | $0.00014 | $0.00368 |
| Haiku 4.5 | $0.00007 | $0.00184 |
Grade A, and why
value-stream-mapping 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 8d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Value Stream Mapping
Load trigger:
"load value-stream-mapping skill"> DORA: AI Capability 2 (Healthy data ecosystems) + AI Capability 7 (Quality internal platforms) Token cost: Medium Prerequisite: At least one dora-measurement snapshot must exist.
Purpose
Identify which stage of the product delivery value stream is absorbing the productivity gains from AI assistance — so investment goes to clearing the actual bottleneck, not the assumed one.
DORA ROI 2026: "Individual productivity gains from AI are often absorbed by downstream disorder — gains in coding speed are swallowed by bottlenecks in testing, security reviews, and complex deployment processes." VSM makes the downstream disorder visible.
Scope boundary: This skill maps the product value stream (idea → user value).
The platform value stream (platform change → fawkes improvement → user benefit) is
handled by fawkes/.agents/skills/value-stream-mapping/ when that skill is written.
When to Use
| Trigger | Signal |
|---|---|
| Lead time high despite fast coding | lead_time_p50_hours > 24hrs but deployment_frequency_per_week < 1 |
| DORA metrics plateau | Two consecutive monthly snapshots show no improvement |
| AI tool adoption not improving throughput | opencode sessions frequent but deploy frequency unchanged |
| Planning a major capability | Before investing in a new stack (uFawkesDevX, uFawkesDORA) |
Measure agent files capability-improvement issues |
>2 issues in same area in one quarter |
The Seven Value Stream Stages
Map each stage for the product being built. Time estimates come from DORA measurement data where available; direct observation otherwise.
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.
- 8d ago First seen · 154 lines · 69 tokens per session scan A ef4637b392e7
value-stream-mapping is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 19d ago), licensed MIT. It adds 69 tokens to every session and 1,839 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-03.
Other skills, from other repositories
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
infrastructure-overview
Top-level skill for the research template infrastructure layer. Use in Cursor, Claude Code, or similar agents when editing or importing anything under infrastructure/, understanding the two-layer architecture, or wiring build/validation/rendering/publishing. Covers module discovery, import patterns, thin…
infrastructure-validation
Skill for the validation infrastructure module providing PDF validation, markdown validation, output integrity checks, link verification, documentation audits, issue categorization, and repository scanning. Use when validating research outputs, checking document quality, running audits, or verifying cross-references.
infrastructure-llm
Skill for the LLM infrastructure module providing local Large Language Model integration via Ollama. Covers client initialization, prompt templates, output validation, manuscript review generation, conversation context, and CLI usage. Use when querying LLMs, generating manuscript reviews, validating LLM outputs, or…
research-workflow
Seven-stage research workflow (SCOPE→LITERATURE→REASON→DESIGN→COMPUTE→SYNTHESIZE→WRITE). Use for: structuring an AI agent's research process, generating literature review prompts, scoping methodology. Usage: from infrastructure.research import ResearchWorkflow; ResearchWorkflow.describe() Config: set stage overrides…
infrastructure-search-literature
Paperclip-style multi-source literature search across arXiv, Crossref, local JSON corpora, and (opt-in) the Paperclip API. Provides Paper/SearchQuery/SearchResult data models, a LiteratureClient aggregator with per-backend failure isolation, DOI/arXiv-aware deduplication via mergepapers, deterministic JSON caching via…