ecp-propose

ecp-propose is a skill for Claude Code from xiaolai/eou-foundry. It costs 21 tokens per session (822 once invoked), scanned A, original, ISC.

A tool for drafting a formal EOU Change Proposal, or ECP, from a diagnosed failure or a planned refactor. An ECP is a recorded request to change how an executable operating unit works.

In plain words
What is it for?
Use it to document the smallest suitable change to an EOU, identify the relevant failure type, and save the proposal in the project's governance records.
Why use it?
It makes the reason, scope, and safeguards for a workflow change explicit before anyone approves it, while preventing proposals that lack a concrete problem or would violate core rules.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the eou-foundry plugin — 14 skills, 1 command shipped together

Install

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.

agentmods
npx agentmods add skills/xiaolai/eou-foundry/ecp-propose
Any agent
npx skills add xiaolai/eou-foundry --skill ecp-propose
Clone the repo
git clone --depth 1 https://github.com/xiaolai/eou-foundry

Made for: Claude Code.

Or install eou-foundry, the plugin that ships this one along with the rest of its 14 skills, 1 command.

Wrote 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.

agentmods badge for ecp-propose

README.md
[![agentmods](https://agentmods.dev/badge/skills/xiaolai/eou-foundry/ecp-propose.svg)](https://agentmods.dev/skills/xiaolai/eou-foundry/ecp-propose)
Your own site
<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>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 822 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 6d ago against content hash bcbeaa6406af, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

codex/skills/ecp-propose/SKILL.md · 70 lines

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

  1. schemas/ecp.schema.yml — field types and constraints
  2. foundry/constitution.yml — invariants the ECP must not violate

Stop conditions

Halt and report before drafting the ECP if:

  • $target does 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_eou cannot be determined from $target.
  • The proposed change would require modifying foundry/constitution.yml — use the constitutional change process instead.

Procedure

  1. Read $target to extract the diagnosed failure or refactor option.
  2. Identify the failure class (F1–F12 from foundry/failure-taxonomy.yml) driving the change.
  3. Determine the smallest change that addresses the root cause without constitutional violation.
  4. Draft the ECP with all required fields (see structure below).
  5. Confirm approval.status is proposed — never set it higher.
  6. Write the ECP to foundry/self-evolution/ecp/proposed/{target_eou}-ecp-{YYYYMMDD}.yml.
  7. 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)

Read the full file on GitHub · 70 lines

Changes

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.

  1. 6d ago First seen · 70 lines · 21 tokens per session scan A bcbeaa6406af

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

microsoft/vscode · 72 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 95 tokens