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-archivegit 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-archive)<a href="https://agentmods.dev/skills/simpleeve/eo-skills/eo-archive"><img src="https://agentmods.dev/badge/skills/simpleeve/eo-skills/eo-archive/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-archive"><img src="https://agentmods.dev/badge/skills/simpleeve/eo-skills/eo-archive.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.00041 | $0.02449 |
| Opus 5 | $0.00020 | $0.01224 |
| Sonnet 5 | $0.00008 | $0.00490 |
| Haiku 4.5 | $0.00004 | $0.00245 |
Grade A, and why
eo-archive 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
eo-archive — 变更归档
归档的本质：把世界结算成 commit，冻结 change 目录为审计历史。change 目录归档后整体冻结，不合并回任何文档。
核心理念
- 四问核对是唯一硬门：change.md §2 逐条过——自动项有证据、人工项验收单已勾、阻塞项不通过禁止归档；豁免必须显式记录
- 冻结不可逆：
status: archived之后 change 目录只读；后续问题按性质走 /eo-fix 或新 change - commit 区间只是审计：归集的区间写入 frontmatter 备查
前置条件
- 必须能找到
.eo-project.json。同目录存在.eo-project.local.json时顶层字段覆盖合并（local 优先）。找不到 → 报错退出，提示运行/eo-project-init - 目标
eo-doc/changes/<change-id>/change.md存在且status: implementing或reviewed（存量done视同 reviewed，顺手改写）- draft/confirmed → 指出当前环节，回 /eo-change 或 /eo-implement；已 archived 直接告知
工作流程（四层）
第一层：四问核对门（唯一硬门）
- 工作区无本 change 的未提交交付改动（业务代码或测试）。有 → 先结算成
[<change-id>]commit 再继续 - §2 逐条核对：
- 自动项：须有验证证据——implement 自验速报 / eo-test 报告（若挂了该闸门）/ 当前重跑。无证据 → 当前重跑补齐，或与用户确认豁免
- 人工项（「人工:」标记）：规范见 ../eo-shared/acceptance.md——非空则
acceptance.md必须存在且与集合一一对应（缺项/孤儿/重复 = 校验失败）；逐项核对勾选与异常行（用户勾的直接有效；agent 代勾必须带确认记录，缺记录按未勾）；验收基线之后存在改变人工项行为的[<change-id>]提交 → 受影响项按未勾（判不清 → 全部按未勾） - 阻塞项不通过/未验 → 禁止归档，按封闭选择协议（../eo-shared/questioning.md §4）三选一：补齐（推荐——回 /eo-fix 循环内分支或 implement 修复；「不通过」= 修复循环输入，status 置回 implementing）/ 显式豁免（§6 记录 + 验收单同项标豁免，双记录同 AC 编号）/ 终止归档
- 非阻塞项不通过 → 记 backlog 继续，不挡归档
- 信号闸门核验：§6 记录了命中信号且未豁免 → 对应闸门报告（test.md / review.md / change-review.md）须存在且结论通过；缺失或结论不通过 → 提示用户补跑或显式豁免（豁免补记 §6）
- brief 与最终交付一致：校对 frontmatter
brief，不符就地改写（口径见 ../eo-shared/summary.md） - 交付证据面核对：
evidence.md存在且「入口与环境 / 过程证据 / 怎么验」三段非空（规范见 ../eo-shared/evidence.md）。缺失或必备段为空 = 校验失败 → 按封闭选择协议（../eo-shared/questioning.md §4）三选一：补齐（回 implement 或 /eo-fix 循环内分支）/ 显式豁免（§6 记录）/ 终止归档——不静默放行 - 归档前先发交付汇报，与确认提问同条消息发出（封闭选择，跨会话最终复核）：
- 交付汇报 = 回复契约四条（../eo-shared/reply-contract.md：做了什么 / 为什么这么做 / 主要产出 / 遇到的问题与解法）+ 证据面渲染（引 evidence.md 的入口地址、截图指针、验收指引——引用不重建）+ 核对结果汇总一句
- 汇报之后才是封闭选择确认项；尚有未勾人工项 → 主动提议「带我验收」逐项走查；核对通过后同步勾 change.md 的人工 AC
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 · -110 lines · -4 tokens per session b4714e74ad2a
- 9d ago First seen · 190 lines · 45 tokens per session scan A a7989f3b6f96
eo-archive is a skill published in the GitHub repository SimpleEve/eo-skills (31 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 2,449 once invoked, about $0.0002 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
ship-it
A GitHub workflow for finishing an implemented issue: commit the relevant changes, push a branch, create a pull request, merge it, and close the issue. GitHub is a service for hosting code and reviewing changes, and a pull request is a proposed change for review.
git-master
Git expert combining atomic commits, rebase/squash, and history search (blame, bisect, log -S). Use for any git operations requiring structured commit strategies, history rewriting, or code archaeology. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
git-bisect-assistant
Automatically performs git bisect to identify the first bad commit that introduced a bug or failure. Use when debugging regressions, tracking down when a test started failing, or identifying which commit broke functionality. Handles flaky tests with retry logic and provides comprehensive reports with bisect logs and…
semantic-szz-analyzer
Identify bug-introducing commits using semantic analysis that extends traditional SZZ algorithm. Distinguishes semantic changes from refactorings or code movements using control-flow and data-flow similarity analysis. Use when analyzing bug-fix commits to trace back to bug-introducing changes, investigating software…
szz-bug-introducing-commit-identifier
Identifies bug-introducing commits using SZZ-style analysis based on bug-fixing commits, commit history, and code blame information. Use this skill when you need to trace bugs back to their origin, identify which commits introduced bugs, analyze bug-fix commits to find root causes, perform software repository mining…
ase-meta-commit
Determine commit message for staged Git changes.