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-specifynpx skills add xiaolai/eou-foundry --skill eou-specifygit 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-specify)<a href="https://agentmods.dev/skills/xiaolai/eou-foundry/eou-specify"><img src="https://agentmods.dev/badge/skills/xiaolai/eou-foundry/eou-specify.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.00027 | $0.01417 |
| Opus 5 | $0.00014 | $0.00709 |
| Sonnet 5 | $0.00005 | $0.00283 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
eou-specify 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specify EOU
Convert or repair $candidate into a formal EOU spec.
Inputs
$candidate(required) — path to a candidate YAML file or YAML content describing the EOU to specify. Resolved in this order: direct file path →foundry/self-evolution/candidate-sets/*.yml(search thecandidateslist for an entry whoseidmatches) →foundry/eous/{id}.yml.
Required reading
schemas/eou.schema.yml— required fields, types, and allowed valuesfoundry/constitution.yml— governance invariants the spec must satisfyfoundry/governance.yml— authority-level definitions and lifecycle rules
Stop conditions
Halt and request clarification before proceeding if:
$candidatedoes not resolve to a readable file or cannot be interpreted as candidate data.- The candidate data does not contain enough information to write a concrete
purpose.statementandoperating_hypothesis— do not invent these. - The
schemas/eou.schema.ymlfile does not exist — cannot validate field completeness without it.
Procedure
Step 1: Determine mode
- If
$candidateresolves to a path with no existing spec file → CREATE mode: build a new spec from the candidate data. - If a spec file already exists at the resolved path → REPAIR mode: read the existing spec and fill in missing or invalid fields without changing fields that are already correct.
Step 2: Load source material
Read $candidate to extract: purpose, operational context, known failure modes, authority level, and blast radius.
Step 3: Map all required fields
Populate each group in order:
classification:
function: # generate | specify | validate | diagnose | promote | refactor | audit | propose | activate | implement | retire
target_object: # the artifact or decision this EOU acts on
automation_mode: # deterministic | LLM_assisted | hybrid | human_executed
authority_level: # suggest_only | draft_only | write_candidate | write_inactive | mutate_active | approve | publish
risk_level: # low | medium | high | critical
lifecycle_stage: # candidate | draft | simulated | pilot | active | monitored | stable | deprecated | retired
purpose:
statement: # one sentence — what this EOU does
non_goals: # explicit list of what it must not do
operating_hypothesis: # "Given [inputs], this EOU can [action] without [boundary violation]."
inputs:
required: # files or data this EOU cannot run without
optional: # files that improve output quality if present
forbidden_assumptions: # things the EOU must not silently assume
context_manifest:
source_of_truth: # canonical files (registry, constitution, schemas)
supporting: # reference files (taxonomy, patterns, maturity model)
forbidden: # files this EOU must not read or mutate
execution:
steps: # ordered, concrete, bounded steps — no "perform bounded operation"
decision_points: # named branch conditions with explicit resolution criteria
stop_conditions: # observable states that stop execution before completion
allowed_tools: # explicit tool list
prohibited_actions: # explicit prohibitions
outputs:
primary: # concrete file path(s) — no placeholder labels
secondary: # supplementary artifacts
trace: # always: foundry/runs/{eou_id}/{run_id}.yml
success_criteria:
must_pass: # binary, verifiable conditions
should_pass: # quality checks that are not hard blockers
validation:
deterministic: # machine-checkable: field presence, schema conformance, count limits
judgment: # audit-level checks that require human or LLM review
red_team: # adversarial scenarios to test boundary robustness
failure_modes:
known: # named failure patterns
warning_signs: # observable signals that a known failure is occurring
repair_actions: # concrete responses to each warning sign
escalation:
require_human_when: # observable conditions that mandate human review
require_approval_for: # actions that cannot proceed without human approval
responsibility:
executor: # Claude | script | human (pick one primary; hybrid: name the split)
reviewer: # who reviews outputs
approver: # who approves lifecycle transitions
cannot_delegate: # non-delegable authorities
blast_radius:
allowed_scope: # directories or files this EOU may write to
forbidden_scope: # directories or files this EOU must never touch
versioning:
supersedes: # prior EOU IDs replaced by this spec
changelog: # list of version entries
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 · 129 lines · 27 tokens per session scan A 013b1dba7a02
eou-specify is a skill published in the GitHub repository xiaolai/eou-foundry (10 stars, last pushed 12d ago), licensed ISC. It adds 27 tokens to every session and 1,417 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…
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…
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…