generate-captured-workflow-from-references

generate-captured-workflow-from-references is a skill for Claude Code from xiaolai/eou-foundry. It costs 85 tokens per session (2,251 once invoked), scanned A, original, ISC.

A tool for turning a goal, reference examples, constraints, and user input into a captured workflow. A captured workflow is a structured description of how work should be done in a particular application or domain.

In plain words
What is it for?
Use it to prepare the structured workflow and values information needed to generate candidate EOUs for an application.
Why use it?
It helps people describe a workflow in an unfamiliar field by organizing examples, boundaries, audience, budget, time, risk, and desired results.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: $skill-name invocation.

Part of the eou-foundry plugin — 14 skills, 1 command shipped together

Good fit Use it to prepare the structured workflow and values information needed to generate candidate EOUs for an application.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xiaolai/eou-foundry/generate-captured-workflow-from-references
Install

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.

Any agent
npx skills add xiaolai/eou-foundry --skill generate-captured-workflow-from-references
Clone the repo
git clone --depth 1 https://github.com/xiaolai/eou-foundry

Made for: Claude Code.

Or install eou-foundry, the plugin that ships this one along with the rest of its 14 skills, 1 command.

Wrote 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.

agentmods badge for generate-captured-workflow-from-references

README.md
[![agentmods](https://agentmods.dev/badge/skills/xiaolai/eou-foundry/generate-captured-workflow-from-references/github.svg)](https://agentmods.dev/skills/xiaolai/eou-foundry/generate-captured-workflow-from-references)
Your own site
<a href="https://agentmods.dev/skills/xiaolai/eou-foundry/generate-captured-workflow-from-references"><img src="https://agentmods.dev/badge/skills/xiaolai/eou-foundry/generate-captured-workflow-from-references/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.

agentmods 80×15 button for generate-captured-workflow-from-references

Your own site · 80×15
<a href="https://agentmods.dev/skills/xiaolai/eou-foundry/generate-captured-workflow-from-references"><img src="https://agentmods.dev/badge/skills/xiaolai/eou-foundry/generate-captured-workflow-from-references.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,251 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00085 $0.02251
Opus 5 $0.00043 $0.01125
Sonnet 5 $0.00017 $0.00450
Haiku 4.5 $0.00009 $0.00225

Measured 9d ago against content hash 1f1aa25f79f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

generate-captured-workflow-from-references 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 9d 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.

codex/skills/generate-captured-workflow-from-references/SKILL.md · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Generate Captured Workflow from References

Synthesize a Stage 0 captured_workflow for $app from a structured reference set and constraints.

What this skill does

One sentence — synthesize the inputs that D2.4 step 6 ($generate-eou-candidates) needs, plus the per-app constitutional domain_values layer, from a user goal + 5-role reference set + constraints + explicit user contributions.

Inputs required

  • $app (required) — the app or domain identifier; used in the output filename cw-{slug}.yml.
  • user_goal (required) — outcome category in plain language ("I want to make X").
  • reference_set (required) — mapping with all 5 role slots filled, each with {ref, why} entries:
    • aspirational — what the user wants to make
    • anti_reference — similar surface, wrong soul
    • boundary_case — edge of the field
    • mainstream_baseline — the median of the field
    • outlier — "I dislike this but it succeeds" (mandatory V1 defense against blind-spot encoding)
  • constraints (required) — audience, scale, budget, time, risk_tolerance, desired_effect.
  • negative_constraints (required) — what the user rejects explicitly.
  • user_contributed_references (required) — ≥1 reference per role slot that the AI did not propose (V2 anti-abdication enforcement).
  • starter_pack (optional) — engine/starter-packs/{domain}.yml if present and the user opts in.

Inputs forbidden

  • Pre-existing workflow prose — that input belongs to $generate-eou-candidates, not this skill. If the user can already articulate a workflow, this skill returns the operational_value_test reject decision and recommends $generate-eou-candidates directly.

Required reading

  1. schemas/captured-workflow.schema.yml
  2. dev-docs/06-values-over-rules.md
  3. dev-docs/08-stage-0-design.md
  4. engine/meta-eous/generate-captured-workflow-from-references.yml

Stop conditions

Halt and report if any of the following hold:

  • Any role slot is empty after best-effort elicitation.
  • user_contributed_references is empty for any slot (V2 violation).
  • Fewer than 3 surviving domain_values after inclusion-test filtering.
  • More than 8 surviving domain_values (cap mirrors foundry V1–V8 sizing).
  • Counterfactual swap audit reveals fewer than 3 flips out of 5 tests (the value layer is decoration).
  • User can articulate a workflow unaided (skill is the wrong tool; use $generate-eou-candidates directly).
  • The app is governance scaffolding only with no real craft domain.

Read the full file on GitHub · 140 lines

Changes

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.

  1. 9d ago First seen · 140 lines · 85 tokens per session scan A 1f1aa25f79f8

Subscribe to this mod's changes

generate-captured-workflow-from-references is a skill published in the GitHub repository xiaolai/eou-foundry (10 stars, last pushed 16d ago), licensed ISC. It adds 85 tokens to every session and 2,251 once invoked, about $0.0004 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens