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 HypoxanthineOvO/Hypo-Workflow --skill cleanupgit clone --depth 1 https://github.com/HypoxanthineOvO/Hypo-WorkflowWrote 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/hypoxanthineovo/hypo-workflow/cleanup)<a href="https://agentmods.dev/skills/hypoxanthineovo/hypo-workflow/cleanup"><img src="https://agentmods.dev/badge/skills/hypoxanthineovo/hypo-workflow/cleanup/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/hypoxanthineovo/hypo-workflow/cleanup"><img src="https://agentmods.dev/badge/skills/hypoxanthineovo/hypo-workflow/cleanup.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.00064 | $0.00538 |
| Opus 5.5 | $0.00026 | $0.00215 |
| Sonnet 5.5 | $0.00013 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
hypo-workflow-cleanup 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
清理：给执行清理的 Agent 看
Agent 会照着仓库里已有的写法继续写，烂写法也会被复制，文档和规则也越积越多。清理按项目自己的标准，把这些一次收拾掉。全程中文，说话短。
标准
- 以 RULES.md 和需求文件为准，尤其是“不能坏”。不按自己的口味重写能用的代码。
- 每一处都问：删掉它，会有人或 Agent 因此出错吗？不会就删；会，就留着或改写。
动手前
- 跑 hw check，把它报出来的东西当线索。
- 找这几类：
- 没人调用的代码、重复实现的工具函数、只为“以后可能用”留的接口。
- 和代码对不上的文档：需求文件的“现在”“代码”锚点、README 里的命令和说明。
- 过时或重复的规则：RULES.md、分区 AGENTS.md 里已经不成立、或者说了两遍的条目。
- 先把清单给用户看：每处删什么、改成什么、为什么。用户确认后再动手。
动手
- 按清单做，不顺手扩大范围。碰到“不能坏”的东西、或者删了会改变用户能看到的行为，停下来问。
- 改代码时，同步改牵连到的需求条目和文档；文档按“只写现在”改写，不追加说明。
- 每处理完一类单独提交，提交格式照 AGENTS.md。
收尾
- 跑测试和 hw check。
- 在对话里汇报：删了什么、改了什么、哪些按用户意见留下了、还有哪些拿不准等用户决定。
不要做
- 不为了让检查变绿删测试、放宽断言或吞掉报错。
- 不改 AGENTS.md：它由 Workflow 安装和升级。
- 不动文档地图外的文件和
archive/里的旧记录。
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 · 40 lines · 64 tokens per session scan A 531651660b83
hypo-workflow-cleanup is a skill published in the GitHub repository HypoxanthineOvO/Hypo-Workflow (24 stars, last pushed 4d ago), licensed MIT. It adds 64 tokens to every session and 538 once invoked, about $0.0003 per session on Opus 5.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-10-21.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.