Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add xiaolai/eou-foundry/plugin install 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-foundry-init)<a href="https://agentmods.dev/skills/xiaolai/eou-foundry/eou-foundry-init"><img src="https://agentmods.dev/badge/skills/xiaolai/eou-foundry/eou-foundry-init.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.1 | $0.00059 | $0.01081 |
| Opus 5 | $0.00030 | $0.00541 |
| Sonnet 5 | $0.00012 | $0.00216 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
eou-foundry-init 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 6d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize EOU-Governed Application
You are scaffolding a new EOU-governed application. The user is invoking this from a workspace directory and should supply an app name.
1. Get the app name
If the user supplied an app name in their request, use it. Otherwise ask: "What is the application's slug name? (lowercase, alphanumeric + hyphen)"
Optional inputs:
- A one-line description of what the application does (defaults to the slug)
NO_GIT=1— set this environment variable before the command to skipgit initin the new directory (default: initialize git)
Validate the slug. Reject names containing /, \, .., a leading ., or any character outside [a-z0-9-]. Refuse to overwrite an existing directory.
2. Run init script
${PLUGIN_ROOT}is the Codex runtime env var for the plugin root. The Claude Code equivalent is${CLAUDE_PLUGIN_ROOT}. Both resolve to the same directory — the name differs by runtime.
Run bash "${PLUGIN_ROOT}/scripts/init_app.sh" "$APP_NAME" "$DESCRIPTION" $([ "$NO_GIT" = "1" ] && echo "--no-git") and let the script handle the existence check and scaffolding atomically. Report what it produced.
3. What the script does (for reference)
scripts/init_app.sh is idempotent in the sense of "refuse to clobber":
- Refuses if
./<app-name>/already exists. - Creates
./<app-name>/and inside it:foundry/populated fromtemplates/— constitution, governance, registry (empty), maturity-model, failure-taxonomy, refactoring-patterns, runtime-contract, meta-eous/, templates/eou-template, templates/generating-eou-template.foundry/eous/,foundry/incidents/,foundry/audits/,foundry/runs/,foundry/self-evolution/{ecp/{proposed,approved,implemented,rejected},regression/cases,upstream/proposed-to-plugin}/empty.CLAUDE.md,AGENTS.md,GEMINI.mdminimal starters..claude/settings.jsonminimal scaffold (no hooks)..gitignorewith the standard AI-tool ignores.README.mdone-paragraph application overview.
- Substitutes
{{APP_NAME}}and{{DESCRIPTION}}placeholders in the template files. - Unless
--no-git, runsgit initand makes a single initial commit. - Runs
python3 "${PLUGIN_ROOT}/scripts/validate_foundry.py"against the new app to confirm the scaffold passes the schema check.
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.
- 6d ago First seen · 83 lines · 59 tokens per session scan A 635adfac6dc1
eou-foundry-init is a skill published in the GitHub repository xiaolai/eou-foundry (10 stars, last pushed 13d ago), licensed ISC. It adds 59 tokens to every session and 1,081 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-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…