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 agentmods add skills/astordu/qoderharness/agents-md-refactornpx skills add astordu/qoderharness --skill agents-md-refactorgit clone --depth 1 https://github.com/astordu/qoderharnessWrote 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/astordu/qoderharness/agents-md-refactor)<a href="https://agentmods.dev/skills/astordu/qoderharness/agents-md-refactor"><img src="https://agentmods.dev/badge/skills/astordu/qoderharness/agents-md-refactor.svg" alt="Measured on agentmods" 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 | $0.00086 | $0.00563 |
| Opus 5 | $0.00043 | $0.00282 |
| Sonnet 5 | $0.00017 | $0.00113 |
| Haiku 4.5 | $0.00009 | $0.00056 |
Grade A, and why
agents-md-refactor 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 4d 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
重构 AGENTS.md
将现有 AGENTS.md 按渐进披露原则重构为精简根文件 + 独立详情文件。
执行步骤
1. 查找矛盾
读取现有 AGENTS.md 以及它指向的相关文档，识别彼此冲突的指令。对每一处矛盾，先询问用户希望保留哪个版本，再继续。
2. 识别核心内容
只保留应放在根目录 AGENTS.md 中的内容：
- 一句话项目描述
- 包管理器（如果不是 npm）
- 非标准的构建/类型检查命令
- 真正与每一项任务都相关的全局约定
3. 标记可删除内容
识别并建议删除以下类型的指令：
- 冗余：agent 已知的通用知识（如"编写干净的代码"）
- 模糊：无法执行或缺少上下文
- 过时：与仓库实际代码不符
逐一列出，等待用户确认后再删除。
4. 分组其余内容
将剩余指令按逻辑类别组织（如 TypeScript 约定、测试模式、API 设计、Git 工作流），为每个分组创建独立 Markdown 文件。
5. 创建文件结构
输出以下文件：
AGENTS.md # 极简根文件，含指向各详情文件的链接
docs/
├── backend.md # 后端架构与约定
├── frontend.md # 前端架构与约定
└── ... # 按实际分组决定
根 AGENTS.md 模板：
# AGENTS.md
[一句话项目描述]
## 关键约定
- 包管理器：[uv/npm/...]
- [其他全局约定]
## 详细文档
- [后端架构与约定](docs/backend.md)
- [前端架构与约定](docs/frontend.md)
输出语言
所有生成内容使用中文。
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.
- 4d ago First seen · 70 lines · 86 tokens per session scan A c88b0943903e
agents-md-refactor is a skill published in the GitHub repository astordu/qoderharness (21 stars, last pushed 9d ago), licensed MIT. It adds 86 tokens to every session and 563 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…