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 xiaolai/eou-foundry --skill generate-eou-candidatesgit clone --depth 1 https://github.com/xiaolai/eou-foundryWrote 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/xiaolai/eou-foundry/generate-eou-candidates)<a href="https://agentmods.dev/skills/xiaolai/eou-foundry/generate-eou-candidates"><img src="https://agentmods.dev/badge/skills/xiaolai/eou-foundry/generate-eou-candidates/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/xiaolai/eou-foundry/generate-eou-candidates"><img src="https://agentmods.dev/badge/skills/xiaolai/eou-foundry/generate-eou-candidates.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.00035 | $0.01629 |
| Opus 5 | $0.00017 | $0.00814 |
| Sonnet 5 | $0.00007 | $0.00326 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
generate-eou-candidates 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.
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.
Generate EOU Candidates
Generate candidate EOUs from $workflow.
Inputs
$workflow(required) — the workflow to analyze; may be a file path (YAML or Markdown) or a free-text description. If a file path, read it; if text, treat it as the workflow description.workflow_slug— derived from the workflow name or file stem, normalized to lowercase alphanumeric + hyphens (e.g.,code-review-workflow). Used in the output filename.captured_workflow(optional, ECP-0017 / Rule 96) — whenfoundry/captured-workflows/cw-{app_id}.ymlexists with all fourhuman_approvalgates populated, load it. Itsdomain_valuesblock is consulted during candidate scoring per Step 6.5.
Required reading
foundry/constitution.ymlfoundry/registry.ymlfoundry/failure-taxonomy.ymlfoundry/meta-eous/generate-eou-candidates.ymlschemas/eou.schema.yml
Stop conditions
Halt and report if any of the following hold:
- Workflow goal is unclear.
- Desired artifact or output is undefined.
- No failure modes are provided or inferable.
- Responsibility boundary is unclear.
- High-stakes workflow has no identified owner.
Procedure
Step 1 — Summarize the workflow
Extract: what actor does what action to produce what artifact, and what the known failure modes are. State any ambiguities as open questions.
Step 2 — Identify decision boundaries
Locate where the success criterion changes — each boundary is a candidate EOU boundary, not each visible action. Separate deterministic steps (scriptable) from judgment steps (LLM or human required).
Step 3 — Registry diff
For each candidate boundary, check foundry/registry.yml and foundry/eous/ + foundry/meta-eous/:
- Does this candidate duplicate an existing EOU? → record and skip.
- Can it extend an existing EOU? → record the extension recommendation.
- Should it be a refactor instead of a new EOU? → record.
- Would a rule, schema field, validator, stop condition, regression case, or human checklist serve better? → record and prefer that over a new EOU.
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.
- 9d ago First seen · 154 lines · 35 tokens per session scan A 342afd6b3ce3
generate-eou-candidates is a skill published in the GitHub repository xiaolai/eou-foundry (10 stars, last pushed 15d ago), licensed ISC. It adds 35 tokens to every session and 1,629 once invoked, about $0.0002 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…