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 agentmods add skills/xiaolai/eou-foundry/eou-refactornpx skills add xiaolai/eou-foundry --skill eou-refactorgit 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-refactor)<a href="https://agentmods.dev/skills/xiaolai/eou-foundry/eou-refactor"><img src="https://agentmods.dev/badge/skills/xiaolai/eou-foundry/eou-refactor.svg" alt="Measured on agentmods" 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 | $0.00024 | $0.00739 |
| Opus 5 | $0.00012 | $0.00369 |
| Sonnet 5 | $0.00005 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
eou-refactor 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 5d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor EOU
Generate candidate refactor options for $target. Do not apply any change.
Inputs
$target(required) — either an EOU ID (resolved tofoundry/eous/{id}.ymlorfoundry/meta-eous/{id}.yml) or a path to an audit report or diagnosis file. When an audit path is given, the EOU ID is extracted from the report.
Required reading
foundry/refactoring-patterns.yml— canonical refactor types (split, merge, scope-reduction, authority-downgrade, step-extraction, validator-addition, stop-condition-injection, responsibility-separation)foundry/constitution.yml— invariants that constrain any proposed changefoundry/governance.yml— authority boundaries and lifecycle-gate rules; required because refactor options can touch authority_level and blast_radius- The source EOU spec (infer path from
$targetif an audit path is given)
Stop conditions
Halt and report before generating options if:
$targetdoes not identify an EOU ID and one cannot be inferred.- No audit report or incident exists to identify a structural problem — do not generate options from speculation.
- The EOU spec does not exist in
foundry/eous/orfoundry/meta-eous/.
Procedure
- Read
$target(EOU ID or audit report). If it is an audit report, extract the EOU ID and load the corresponding spec. - Identify the structural problems: scope creep, authority inflation, weak validation, missing stop conditions, unbounded steps, ambiguous responsibility, missing trace preservation, blast-radius overreach, and circular EOU dependencies.
- For each structural problem, generate one or more refactor options using the patterns in
foundry/refactoring-patterns.yml. - Include a "no change" baseline option with its trade-offs stated.
- Rank options by: smallest blast radius, then lowest authority required, then easiest rollback.
- For each option that touches authority, approval, or constitutional invariants: mark
requires_ecp: true. - Write the candidate refactor set.
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.
- 5d ago First seen · 71 lines · 24 tokens per session scan A a05d5035b396
eou-refactor is a skill published in the GitHub repository xiaolai/eou-foundry (10 stars, last pushed 12d ago), licensed ISC. It adds 24 tokens to every session and 739 once invoked, about $0.0001 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…