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 wuyaojunkylin/research-digital-curation-skills --skill curatorial-log-method-recoverygit clone --depth 1 https://github.com/wuyaojunkylin/research-digital-curation-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/wuyaojunkylin/research-digital-curation-skills/curatorial-log-method-recovery)<a href="https://agentmods.dev/skills/wuyaojunkylin/research-digital-curation-skills/curatorial-log-method-recovery"><img src="https://agentmods.dev/badge/skills/wuyaojunkylin/research-digital-curation-skills/curatorial-log-method-recovery/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/wuyaojunkylin/research-digital-curation-skills/curatorial-log-method-recovery"><img src="https://agentmods.dev/badge/skills/wuyaojunkylin/research-digital-curation-skills/curatorial-log-method-recovery.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00079 | $0.00417 |
| Opus 5 | $0.00039 | $0.00209 |
| Sonnet 5 | $0.00016 | $0.00083 |
| Haiku 4.5 | $0.00008 | $0.00042 |
Grade A, and why
curatorial-log-method-recovery 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 12d 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
项目日志与方法回收
概述
使用这个 skill 防止长期策展项目丢失判断过程。它记录会影响后续内容、结构、设计和实现的关键决定。
记录什么
记录判断，而不是流水账。应包括：
- 本轮工作背景和测试的问题。
- 被比较的方案。
- 用户或团队反馈。
- 某个方向为什么失败、收窄或被保留。
- 已固定的结论及其适用范围。
- 未解决问题和下一步。
- 可迁移到下一个项目的方法经验。
日志结构
采用简洁结构：
- 日期和阶段。
- 工作背景。
- 测试方向。
- 发现的问题。
- 固定结论。
- 余留问题。
- 下一步工作。
- 可复用方法说明。
自检问题
每轮复盘时询问：
- 策展对象是否仍然清楚？
- 人物、物件、图像或界面效果是否开始替代真正主体？
- 每种页面类型是否仍有明确角色？
- 文本是否已经能落位到模块？
- 材料是在承担证据、定位、分析还是氛围？
- 视觉和技术选择是否服务阅读路径？
- 哪条规则应被带入下一个项目？
输出
输出日志条目、固定结论列表、短自检和可复用方法说明。常规文件修改细节不必记录，除非它影响后续判断。
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.
- 12d ago First seen · 52 lines · 79 tokens per session scan A c8c7edf92a44
curatorial-log-method-recovery is a skill published in the GitHub repository wuyaojunkylin/research-digital-curation-skills (3 stars, last pushed 4mo ago), licensed MIT. It adds 79 tokens to every session and 417 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-31.
Other skills, from other repositories
exhibition-outline
A template for turning an exhibition plan into a three-page presentation outline. The pages cover the theme, its explanation and visitor story, and a detailed area-by-area display plan.
tender-analysis
A workflow for reviewing tender documents, which are formal project requests that describe requirements and bidding rules. It extracts project details, technical and business conditions, deadlines, scoring rules, risks, and questions for clarification.
exhibition-theme-brainstorm
A structured brainstorming method for creating exhibition themes, meaning the ideas and story that guide a museum, company, or institutional display. It develops themes from broad ideas, an organisation’s identity, its values, and possible visual expressions.
interaction-team-deliverables
A design-delivery guide for turning an exhibition plan into instructions that an interaction-design team can implement. It covers interactive exhibits, content-management tools, user experience, visualisation, and switching between multiple visual styles.
tender-booklet-writing
A Chinese-language writing skill for explaining each page of a bid proposal booklet. A bid proposal booklet is a presentation document prepared to respond to a tender or contract request.
ppt-layout
A page-by-page layout guide for turning an exhibition plan into a presentation. It defines each slide’s purpose, text hierarchy, content, visual suggestions, and one-sentence takeaway.