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/ecp-proposenpx skills add xiaolai/eou-foundry --skill ecp-proposegit 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/ecp-propose)<a href="https://agentmods.dev/skills/xiaolai/eou-foundry/ecp-propose"><img src="https://agentmods.dev/badge/skills/xiaolai/eou-foundry/ecp-propose.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.00021 | $0.00822 |
| Opus 5 | $0.00010 | $0.00411 |
| Sonnet 5 | $0.00004 | $0.00164 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
ecp-propose 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Propose ECP
Create a formal EOU Change Proposal (ECP) from $target.
Required reading
schemas/ecp.schema.yml— field types and constraintsfoundry/constitution.yml— invariants the ECP must not violate
Stop conditions
Halt and report before drafting the ECP if:
$targetdoes not identify a concrete failure or refactor option — a goal that names no concrete failure class, incident id, or refactor-option id is not accepted.- The
target_eoucannot be determined from$target. - The proposed change would require modifying
foundry/constitution.yml— use the constitutional change process instead.
Procedure
- Read
$targetto extract the diagnosed failure or refactor option. - Identify the failure class (F1–F12 from
foundry/failure-taxonomy.yml) driving the change. - Determine the smallest change that addresses the root cause without constitutional violation.
- Draft the ECP with all required fields (see structure below).
- Confirm
approval.statusisproposed— never set it higher. - Write the ECP to
foundry/self-evolution/ecp/proposed/{target_eou}-ecp-{YYYYMMDD}.yml. - Record the run in
foundry/runs/{eou_id}/{run_id}.yml.
Required ECP fields
Field names match schemas/ecp.schema.yml. Do not use the old names (eou_id, observed_problem, simulation_status, required_tests).
id: # ecp-{target_eou}-{YYYYMMDD}
target_eou: # ID of the EOU being changed
target_version_from: # current version of the EOU (e.g. "0.2.0")
target_version_to: # intended version after this change (e.g. "0.3.0")
failure_class: # F1-F12 taxonomy code(s) — supplementary, not schema-required
problem: # Concrete failure symptom, not a vague label
proposed_change: # One specific structural change (scope, steps, inputs, authority, blast_radius, validators, stop_conditions, approval_requirements, or responsibility boundaries)
expected_benefit: # Observable outcome if the change is applied
risks: # What can go wrong; who is affected
tests_required: # List of regression case IDs or new test fixtures to add
simulation: # not_run | run_pass | run_fail
approval:
status: # must be "proposed" — never "approved" from this EOU
approver: # left blank until human owner approves
rollback_considerations: # How to revert if the change degrades outcomes (supplementary)
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 · 70 lines · 21 tokens per session scan A bcbeaa6406af
ecp-propose is a skill published in the GitHub repository xiaolai/eou-foundry (10 stars, last pushed 12d ago), licensed ISC. It adds 21 tokens to every session and 822 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…