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 eou-promotegit 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/eou-promote)<a href="https://agentmods.dev/skills/xiaolai/eou-foundry/eou-promote"><img src="https://agentmods.dev/badge/skills/xiaolai/eou-foundry/eou-promote/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/eou-promote"><img src="https://agentmods.dev/badge/skills/xiaolai/eou-foundry/eou-promote.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.00044 | $0.01005 |
| Opus 5 | $0.00022 | $0.00502 |
| Sonnet 5 | $0.00009 | $0.00201 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
eou-promote 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evaluate EOU Lifecycle
Evaluate $eou_id against the maturity model and produce a lifecycle recommendation.
This skill has function: promote — it evaluates and recommends. It does not
execute lifecycle transitions. The human owner executes promotion via activate
and retirement via retire after approving this recommendation.
Inputs
$eou_id(required) — the EOU identifier to evaluate; must match a spec file and registry entry.target_stage(optional) — the lifecycle stage to transition to; if omitted, infer the logical next stage from the gate table.
Required reading
foundry/maturity-model.yml— promotion gate requirements per lifecycle stagefoundry/registry.yml— current registration status and lifecycle stagefoundry/governance.yml— approval authority for lifecycle transitions
Also read (to evaluate evidence)
foundry/audits/eou-audits/{eou_id}.audit.yml— most recent audit (required fordraft → pilotand above)foundry/self-evolution/regression/cases/*.yml— filter to YAML files where theeou_idfield equals$eou_id— regression coveragefoundry/runs/— scan fortrace.ymlfiles containingeou_id: {eou_id}— execution traces required forpilot → active
Promotion prerequisites (all must be satisfied)
| Gate | Required evidence |
|---|---|
candidate → draft |
At least one complete spec pass and one failed-case regression fixture |
draft → simulated |
Spec complete, dry-run or sandbox trace available, no open critical findings |
draft → pilot |
Passed eou-audit, ECP approved for any open findings, human owner on record |
pilot → active |
Minimum 3 successful pilot traces, zero open critical findings, human owner approval |
active → monitored |
Elevated-risk event or audit finding requiring close observation; no gate, owner decision |
monitored → stable |
Minimum 5 clean traces post-monitoring period, zero open high/critical findings |
stable → active |
Reverse to active when monitoring obligation lapses; owner decision |
Any → deprecated |
Owner decision recorded; replacement EOU or alternative documented |
Any → retired |
Superseded by successor EOU or determined to have no operational value; archived, not deleted |
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 · 88 lines · 44 tokens per session scan A 13bdf0779ea4
eou-promote is a skill published in the GitHub repository xiaolai/eou-foundry (10 stars, last pushed 16d ago), licensed ISC. It adds 44 tokens to every session and 1,005 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…