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-project-recordgit 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-project-record)<a href="https://agentmods.dev/skills/simpleeve/eo-skills/eo-project-record"><img src="https://agentmods.dev/badge/skills/simpleeve/eo-skills/eo-project-record/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-project-record"><img src="https://agentmods.dev/badge/skills/simpleeve/eo-skills/eo-project-record.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.00138 | $0.00926 |
| Opus 5 | $0.00069 | $0.00463 |
| Sonnet 5 | $0.00028 | $0.00185 |
| Haiku 4.5 | $0.00014 | $0.00093 |
Grade A, and why
eo-project-record 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.
What it actually says
eo-project-record
功能
项目记忆的统一写入口，两种记录类型、两个目录、各自 INDEX：
| 类型 | 目录 | 记什么 | 谁消费 |
|---|---|---|---|
| lesson | <project_root>/lessons/ |
踩坑、最佳实践、意外收获 | eo-change / eo-implement / eo-fix 启动时按 trigger 自动消费 |
| decision | <project_root>/decisions/ |
关键决策：背景、候选、裁定、理由 | eo-recall 缘由瀑布（以及一切「当初为什么」的场景） |
分不清类型时的判据：教训回答「下次怎么做」，决策回答「当时为什么这么定」。一次对话产出两者都有 → 各记一条，互相 [[链接]]。
前置
必须能找到 .eo-project.json。同目录存在 .eo-project.local.json 时顶层字段覆盖合并（local 优先）。找不到 → 报错退出，提示运行 /eo-project-init。从中读取 project_root / project_name。
执行步骤
1. 判型与提炼
从用户输入判定类型（lesson / decision），提炼标题与核心内容。两个目录均 lazy 创建。
2a. lesson 类型
格式严格按 ../eo-shared/lessons.md §2（结论前置：规则 → 适用条件 → 背景；frontmatter 必填 trigger 与 summary 检索锚点）；文件 lessons/<YYYY-MM-DD>-<slug>.md；同步维护 lessons/INDEX.md（格式见 lessons.md §3）。
2b. decision 类型
按 references/decision-template.md 写入 decisions/<YYYY-MM-DD>-<slug>.md；同步维护 decisions/INDEX.md（表格：日期 / 标题链接 / status / summary）。
注意分工：流程内的决策不用进来——change 起草的已钉决策落 change.md §1、brainstorming 的落其记录「关键决策」表。本类型只收流程外的重大决策（方向取舍、架构选型、规则变更这类会被将来反复问「当时为什么」的）。
3. 收尾
- 输出：文件路径 + 一句话摘要 + 该目录累计条数
- 内容涉及已有记录的修正 → 旧文件
status改superseded并在顶部指向新条目（正文不改）
reindex（存量迁移动作）
用户说「reindex lessons / reindex decisions / 迁移旧记录」时：扫描对应目录全部文件——缺 trigger（仅 lesson）/summary/status 的，读正文提炼后只回填 frontmatter（正文一字不动）；重建该目录 INDEX.md。幂等，可重复跑。
约束
- 记录文件正文创建后不改，补充走新建；唯一例外是
status: superseded标注 - 每次写入必须同步对应 INDEX——没进索引的记录等于没写（消费方只扫 INDEX）
- 记录按项目隔离；仅用户明确要求时写入，不做关键词嗅探
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 First seen · 53 lines · 138 tokens per session scan A c10b6a8d111e
eo-project-record is a skill published in the GitHub repository SimpleEve/eo-skills (31 stars, last pushed 2d ago), licensed MIT. It adds 138 tokens to every session and 926 once invoked, about $0.0007 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-09-04.
Other skills, from other repositories
close-my-loops
Build and maintain a personal work profile and open-loop tracker for the user's own job — a markdown file covering their org, key contacts, communication style, active initiatives, and open loops synthesized from their own email/Slack; a Cowork Project setup so that file is actually read every session; a scheduled…
project-compass
Map the tribal knowledge of a codebase into per-area COMPASS.md files — the why, the gotchas, and how each area connects — for existing repos and as they grow. Use when the user says "map this codebase", "generate compass files", "refresh the compass", or after a significant area changes.
aisee:reflect
A guide for reviewing a work session and saving reusable lessons as project documents. It distinguishes temporary suggestions from confirmed long-term team knowledge and from records of specific solved problems.
aisee:knowledge-curate
A review process for turning project notes into reusable team-knowledge drafts. It checks candidate lessons for private details, duplicates, outdated information, and usefulness beyond one project.
failure-mode-capture
Record a "don't do X here, it breaks Y" lesson into AGENTS.md so an agent doesn't repeat a mistake. Dedupes against CLAUDE.md/instincts before writing, promotes generalizing lessons out of memory, and keeps AGENTS.md under budget. Use after a bug, regression, or near-miss, or when the user says "capture this" / "make…
handoff
Carry essential working context to another task, directory or worktree, harness, collaborator, or mid-phase side fork in a portable Markdown handoff.