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/simpleeve/eo-skills/eo-implementnpx skills add SimpleEve/eo-skills --skill eo-implementgit 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-implement)<a href="https://agentmods.dev/skills/simpleeve/eo-skills/eo-implement"><img src="https://agentmods.dev/badge/skills/simpleeve/eo-skills/eo-implement.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 | $0.00079 | $0.02491 |
| Opus 5 | $0.00039 | $0.01246 |
| Sonnet 5 | $0.00016 | $0.00498 |
| Haiku 4.5 | $0.00008 | $0.00249 |
Grade A, and why
eo-implement 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 yesterday.
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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
eo-implement — 代码实现
按 change.md 实施代码。TODO 按 Batch 分组执行，批末 checkpoint：自验该批对应的 AC、勾选进度、汇报，再决定是否继续。测试是普通工程实践——需要就写，遵循项目既有测试约定。
核心原则
- 严格遵循 change：按 §5 TODO 逐项实现；发现 change 有问题先告知用户，不自行改方案
- 验收驱动：AC（change.md §2）是完成判据——TODO 全勾 + 自动 AC 自验通过 = 实施完成；人工项归验收单（../eo-shared/acceptance.md）
- 最小变更：只实现 change 要求的内容，不做额外"优化"
- 自验留证：自动 AC 逐条按验证口径执行，命令 + 关键输出留在对话速报
前置条件
- 必须能找到
.eo-project.json。同目录存在.eo-project.local.json时顶层字段覆盖合并（local 优先）。找不到 → 报错退出，提示运行/eo-project-init - 目标
eo-doc/changes/<change-id>/change.md存在且status: confirmed或implementing（reviewed状态下的阻塞反馈修复归 /eo-fix 循环内分支——它会先按回退边置回implementing） - change 不存在 → 提示先执行
/eo-change；status: draft → 提示先在 /eo-change 完成确认
工作流程
-
阅读上下文
- change.md（主输入：§1 意图与已钉决策、§2 AC、§5 TODO、§6 风险）
- 相关代码定位：
.codegraph/索引存在则codegraph explore优先召回；不存在则按目录收敛 + 源码直读，理解入口与既有模式 - lessons 消费：按 ../eo-shared/lessons.md §1 扫 INDEX 匹配 trigger，命中读「规则」节带入
- 涉及 UI 且仓库根有
DESIGN.md→ 读入并遵守
-
首次启动登记
- frontmatter 写入
base_commit: <当前 HEAD>（已有则不动） status: confirmed → implementing（skill 自动改，不要求用户操作）——流转期零投影动作，看板由 archive 收口的eo-sync run或手动同步刷新
- frontmatter 写入
-
确认执行范围
- 列出各 Batch 及 TODO 数，默认从第一个未完成 Batch 开始；用户可指定只跑某批
- 同层并行批（字母后缀，如 Batch 2a/2b）互不干扰，可乱序执行或只跑其一；本 skill 单会话内仍串行执行——跨 worker 并行派发归 /eo-loop（判据/隔离/合流见 ../eo-shared/granularity.md §6）
-
批内逐项实现
- 按依赖顺序编码；每完成一个 TODO 立即在 change.md 勾选——勾选门 = 常规绿灯（编译/lint/相关测试）
- 测试随写：逻辑密集、边界多、会被后续变更反复触碰的验证点落成测试文件（遵循项目既有目录与命名约定）；其余靠一次性执行证据。写测试不是流程义务，是工程判断
- 写码时注释零溯源：change/TODO/AC/finding 等流程标记不进注释，也不写「为何正确」的叙事注释（项目级完整纪律见
eo-doc/agent-handbook/comments.md，如已启用） - 遇到 change 未覆盖的技术细节：能从代码自答的自答；真正的决策问用户（一次 1-2 问）；发现要改的是前序 change 已引入并生效的对外契约/行为 → 按 ../eo-shared/questioning.md §4「破坏性变更类问题」强制问直接替换还是保留兼容，不得自答代入，结论回补 change.md §1
- 发现 TODO/AC 写漏：告知用户，经确认后就地补进 change.md（意图不变的精化），再继续；补的是人工项且验收单已生成 → 同步补验收项（未勾）
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.
- yesterday Changed · -19 lines · +25 tokens per session 763b56488c4d
- 5d ago First seen · 105 lines · 54 tokens per session scan A 9e714c392b4e
eo-implement is a skill published in the GitHub repository SimpleEve/eo-skills (31 stars, last pushed 3d ago), licensed MIT. It adds 79 tokens to every session and 2,491 once invoked, about $0.0004 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
article-icons
Illustrate an article (Markdown, HTML, etc.) with animated-style icons from itshover.com/icons. Fetches icons as clean inline SVG and places them at section headings, key concepts, lists, and callouts. Triggers on: /article-icons, 配图, 给文章配图标, add icons to article, illustrate with icons.
scenario-generator
Generate comprehensive test scenarios, user stories, and acceptance criteria from requirements and specifications. Use this skill when planning testing efforts, writing user stories, creating test cases, documenting acceptance criteria, exploring edge cases, designing test coverage, or translating requirements into…
traceability-matrix-generator
Builds traceability matrices connecting requirements to design documents to source code implementation, tracking the complete development lifecycle. Use when you need to verify implementation completeness, ensure all requirements are implemented in code, generate compliance documentation, audit requirement coverage…
code-comment-generator
Generates meaningful comments and documentation for code to improve maintenance and readability. Use when adding documentation to Python or Java code, including function/method docstrings, class documentation, inline explanations for complex logic, and code annotations (TODO, FIXME). Analyzes existing comment style in…
code-smell-detector
Identify and report code smells indicating poor design or maintainability issues in Python code, including duplicate code, magic numbers, hardcoded values, God classes, feature envy, inappropriate intimacy, data clumps, primitive obsession, and long parameter lists. Use when conducting code quality audits, preparing…
edge-case-generator
Automatically identify potential boundary and exception cases from requirements, specifications, or existing code, and generate comprehensive test cases targeting boundary conditions, edge cases, and uncommon scenarios. Use this skill when analyzing programs, code repositories, functions, or APIs to discover and test…