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-doc-managergit 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-doc-manager)<a href="https://agentmods.dev/skills/simpleeve/eo-skills/eo-doc-manager"><img src="https://agentmods.dev/badge/skills/simpleeve/eo-skills/eo-doc-manager/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-doc-manager"><img src="https://agentmods.dev/badge/skills/simpleeve/eo-skills/eo-doc-manager.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.00113 | $0.02357 |
| Opus 5 | $0.00056 | $0.01179 |
| Sonnet 5 | $0.00023 | $0.00471 |
| Haiku 4.5 | $0.00011 | $0.00236 |
Grade A, and why
eo-doc-manager 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
eo-doc-manager
代码侧文档管理。项目管理侧（roadmap / decisions / lessons / design / docs）由 eo-project-* skill 管。
前置
除 init 外的所有命令必须能找到 .eo-project.json（cwd 或父目录）。同目录存在 .eo-project.local.json 时顶层字段覆盖合并（local 优先）。找不到 → 报错退出，提示运行 /eo-project-init。
init 通常由 /eo-project-init 内部调用；用户直接调用 /eo-doc-manager init 时，若 .eo-project.json 不存在会提示先走 /eo-project-init。
命令路由
| 命令 | 触发词 | 流程 |
|---|---|---|
init |
初始化文档、init docs | 创建 eo-doc/ 最小骨架（changes/ + agent-handbook/INDEX + templates/） |
modify |
修改文档、整理文档 | 维护 changes/INDEX.md / agent-handbook/ 规范篇 / templates/ |
sync |
同步文档、同步 state、重新生成现状文档 | cursor 增量再生 state/ 现状篇（需 state.enabled，流程见下） |
「查文档 / 当时怎么设计的 / 这个逻辑怎么实现的」→ 走
/eo-recall（本 skill 不提供 query，回归纯维护职责）。
路由规则：
- 明确命令 → 直接路由
- 自然语言 → 按触发词匹配
- 无法判断 → 列出可用命令
目录结构（代码侧 eo-doc/）
所有文档存放在项目根目录 eo-doc/ 下（无顶级 INDEX.md；agent 配置注入段中的目录表即一级索引）：
eo-doc/
├── changes/ # 必建，change 工件流（子目录由 eo-* 工作流 skill 产出）
│ └── INDEX.md # 项目级 change 时间线
├── agent-handbook/ # 可选，Agent 操作手册（篇目含 INDEX.md）
├── state/ # 可选（`state.enabled` 时由 sync 增量再生维护）
└── templates/ # 必建（空），eo-* 技能扩展点
不处理的历史目录
eo-doc/ 下可能存在的历史目录（doc/、dev/、design/、research/、knowledgebase/）：不读取、不重建、不删除，仅供历史查阅；v1 遗留的迁移处理见 eo-skills 仓库的 docs/migration-v1-to-v2.md。
state/ 单独处置：配置 state.enabled: true → 由本 skill sync 维护的活文档层；未启用 → 视同历史目录冻结留存（不删除）。
目录职责
| 目录 | 职责 | 面向 | 核心问题 |
|---|---|---|---|
changes/ |
change 工件流 — 每次变更的 change/review/test 产出 | 都 | "变更进行到哪了？" |
agent-handbook/ |
Agent 操作手册 — 相对固定的操作规范（worktree 协作 / 架构分工 / 目录约定 / UI token 用法 / agent 协作），非 SSOT（代码为准），不挂自动同步 | AI | "操作时按什么规范？" |
state/ |
业务现状活文档 — 模块现状篇（state.enabled 时存在），代码为唯一信源cursor 增量再生，非 SSOT |
都 | "系统现在是什么样？" |
templates/ |
eo-* 技能的扩展点 — 项目类型、工作流定制 | AI | "项目怎么定制？" |
changes/：
- 子目录由 eo-change、eo-implement、eo-review、eo-archive 等技能按约定产出
- 本 skill 负责
changes/INDEX.md的整理与修复（条目对应、孤儿清理、seq 查重）
What ships with it
4 files 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 · -108 lines · +53 tokens per session b396b824875b
- 9d ago First seen · 230 lines · 60 tokens per session scan A f9562732a5eb
eo-doc-manager is a skill published in the GitHub repository SimpleEve/eo-skills (31 stars, last pushed 2d ago), licensed MIT. It adds 113 tokens to every session and 2,357 once invoked, about $0.0006 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.