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 skills add SimpleEve/eo-skills --skill eo-changegit clone --depth 1 https://github.com/SimpleEve/eo-skillsWrote 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/simpleeve/eo-skills/eo-change)<a href="https://agentmods.dev/skills/simpleeve/eo-skills/eo-change"><img src="https://agentmods.dev/badge/skills/simpleeve/eo-skills/eo-change/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/simpleeve/eo-skills/eo-change"><img src="https://agentmods.dev/badge/skills/simpleeve/eo-skills/eo-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00090 | $0.02925 |
| Opus 5 | $0.00045 | $0.01463 |
| Sonnet 5 | $0.00018 | $0.00585 |
| Haiku 4.5 | $0.00009 | $0.00293 |
Grade A, and why
eo-change 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
eo-change — 发起变更
发起一次变更。change 是过程工件：起草期承载澄清与拆解，实施期承载进度，归档即冻结为审计历史——不合并回任何文档。
核心理念
- 四问骨架：change.md 的第一受众是用户。§1 解决什么问题、§2 完成后我应该看到什么、§3 谁验收按什么标准、§4 不通过怎么办——工程细节折叠进 §5 技术备注
- 验收驱动：AC（§2）先于 TODO 产出，是 implement 的完成判据、archive 的验收门、fix 的期望行为锚点
- 默认信任，信号升级：主路只有 change → implement → archive 三站；命中风险信号才建议挂闸门（change-review / test / review），清单与纪律见 ../eo-shared/granularity.md §5
- 量化粒度：超软标建议拆、超硬标拒绝确认，指标数值以 granularity.md §1 为准
- 提问有预算：事实自查、决策上抛——规则见 ../eo-shared/questioning.md
- 状态自动流转：用户在对话里确认，skill 落盘 status，用户永不手改 frontmatter
前置条件
- 必须能找到
.eo-project.json（cwd 或父目录）。同目录存在.eo-project.local.json时顶层字段覆盖合并（local 优先）。找不到 → 报错退出，提示运行/eo-project-init。eo-doc/路径由doc_root解析 eo-doc/changes/不存在时 lazy 创建（含 INDEX.md 骨架）
工作流程
第一步：意图理解
- 读用户的变更描述。若来自 /eo-brainstorming 捕获出口：直接继承其已钉决策与 change 草案，跳过已钉项的一切重复提问，从第四步续起。若来源是某张 backlog 卡：继承卡片的 title/说明/标签作为意图输入，记下卡片路径待确认后归档。若来源是外部 GitHub issue：继承其正文作意图输入，记下 issue 号待落盘回写
issue:（eo-sync 靠回写号去重） - trivial → 主动短路：按 ../eo-shared/granularity.md §2 判据，满足即告知用户「这不值得开 change，直接改」，按直改模式执行（改 → 验证 →
fix:/ui:前缀 commit；注释零溯源，见 ../eo-shared/conventions.md §2.6），本流程终止 - 方向未定 → 建议升级：「这个方向本身还没定，建议先 /eo-brainstorming 把决策钉了再回来」；用户坚持则继续，澄清预算放宽到 5+
- update vs new：若变更明显是某个未归档 change 的意图精化 → 提议就地更新那个 change 而非新开（决策表见 granularity.md §3）
第二步：事实自查（静默执行）
提问之前先自答：
- 定位相关现状与实现：
.codegraph/索引存在则codegraph explore优先召回；不存在则按目录收敛 + 源码直读相关段落 - 读
eo-doc/changes/INDEX.md最近 3 条（演化方向，避免重复/冲突） - lessons 消费：按 ../eo-shared/lessons.md §1 扫 INDEX 匹配 trigger/tags，命中 ≤3 条读其「规则」节带入起草；采纳的在 §1 已钉决策标注来源
- 涉及外部世界 → 按 ../eo-shared/research.md 消费规则查
<project_root>/research/ - 涉及 UI 且仓库根有
DESIGN.md→ 读入作为默认设计约束 - 能从以上信源回答的问题，禁止问用户
第三步：预算内澄清
按 ../eo-shared/questioning.md 全文执行：预算配比、每轮 1-2 问、封闭选择按其 §4 协议（带推荐项）、视觉/UI 方向类问题必带「画 HTML 对比页」选项、疲劳信号立即降级用默认。defer 上限 3 条，落入 §6 开放问题。
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · -102 lines · +24 tokens per session 97066ec99883
- 9d ago First seen · 223 lines · 66 tokens per session scan A 76249d244158
eo-change is a skill published in the GitHub repository SimpleEve/eo-skills (31 stars, last pushed 2d ago), licensed MIT. It adds 90 tokens to every session and 2,925 once invoked, about $0.0005 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-30.
Other skills, from other repositories
to-issues
A planning aid that breaks a PRD or technical specification into small implementation issues, each covering a complete, demonstrable piece of work.
github-triage
Unified GitHub triage for issues AND PRs. Classifies open items, answers questions from codebase, analyzes bugs, reviews PRs, and produces a structured triage report. Triggers: 'triage', 'triage issues', 'triage PRs', 'github triage'.
issue-report-generator
Automatically generate clear, actionable issue reports from failing tests and repository analysis. Analyze test failures to understand expected vs. actual behavior, identify affected code components, and produce well-structured Markdown reports suitable for GitHub Issues or similar trackers. Use when a test fails…
python-repo-quickstart
Quickly analyzes Python repositories to understand their purpose, structure, and setup requirements. Use when Claude needs to onboard to a new Python codebase, understand project structure, identify entry points, determine dependencies, or generate setup instructions. Trigger when users ask to "analyze this Python…
openase-platform
Platform operations for tickets, projects, and runtime coordination inside OpenASE.
ticket-workpad
Maintain the persistent ticket work log comment on the current ticket and use it as the execution log.