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/init_qoder_harnessnpx skills add astordu/qoderharness --skill init_qoder_harnessgit clone --depth 1 https://github.com/astordu/qoderharnessWhat 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.00037 | $0.01596 |
| Opus 5 | $0.00018 | $0.00798 |
| Sonnet 5 | $0.00007 | $0.00319 |
| Haiku 4.5 | $0.00004 | $0.00160 |
Grade A, and why
init_qoder_harness 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 3d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
初始化 Qoder Harness
搭建工程技能所假定的、按仓库划分的配置：
- Issue tracker——issue 存放在哪里（默认 GitHub；本地 markdown 也开箱即用地受支持）
- 分诊标签（Triage labels）——用于五个规范分诊角色的字符串
这是一个由提示词驱动的技能，而非一个确定性脚本。探索、呈现你的发现、与用户确认，然后再写入。
流程
1. 探索
查看当前仓库以理解它的初始状态。阅读已存在的东西；不要假设：
git remote -v和.git/config——这是一个 GitHub 仓库吗？哪一个？- 仓库根目录的
AGENTS.md和CLAUDE.md——有哪个存在吗？其中是否已有一个## Agent skills小节？ docs/agents/——这个技能之前的输出是否已经存在？.scratch/——本地 markdown issue tracker 约定已在使用中的迹象triage技能安装了吗？（与本技能并列的一个triage技能文件夹，或你可用技能中的triage。）这决定 B 节是否会运行。
2. 呈现发现并询问
概述有什么、缺什么。然后按顺序处理各小节——一节，一个回答，再到下一节。
每一节都以推荐的答案开头，好让用户一个字就能接受它。只在选择确实产生分支时给一句解释；当探索已经把它敲定时就整节跳过（triage 未安装时跳过 B 节）。
A 节——Issue tracker。
解释：所谓 "issue tracker" 是本仓库 issue 存放的地方。像
to-tickets、triage、to-spec和qa这样的技能会从中读取、也向其写入——它们需要知道到底该调用gh issue create、在.scratch/下写一个 markdown 文件，还是遵循你描述的某种其他工作流。选你实际为本仓库跟踪工作的地方。
默认姿态：这些技能是为 GitHub 设计的。如果某个 git remote 指向 GitHub，就提议它。如果某个 git remote 指向 GitLab（gitlab.com 或自托管主机），就提议 GitLab。否则（或如果用户更倾向），提供：
- GitHub——issue 存放在仓库的 GitHub Issues 中（使用
ghCLI） - GitLab——issue 存放在仓库的 GitLab Issues 中（使用
glabCLI） - 本地 markdown——issue 作为本仓库
.scratch/<feature>/下的文件存放（适合单人项目或没有远端的仓库） - 其他（Jira、Linear 等）——请用户用一段话描述工作流；技能会把它记录为自由格式的散文
把选择记录在 docs/agents/issue-tracker.md 中。GitHub 和 GitLab 模板带有一个 "PRs as a request surface（把 PR 作为请求来源）" 标志，默认 关闭——保持关闭、不要主动提起；想把外部 PR 纳入分诊队列的用户日后可以在文件里翻开这个标志。
B 节——分诊标签词汇。 如果 triage 技能未安装（探索已经告诉你了），就整节跳过——一个未安装的技能不需要标签。
如果它确实安装了，只问一个问题：
你想保留默认的分诊标签吗？（推荐：是）
默认值是五个规范角色，每个标签字符串都等于其名称：needs-triage、needs-info、ready-for-agent、ready-for-human、wontfix。选 是，就原样写入。只有当用户说不时——通常是因为他们的 tracker 已经用了其他名称（例如用 bug:triage 表示 needs-triage）——才收集这些覆盖项，好让 triage 应用现有标签而不是创建重复的。
3. 确认并编辑
向用户展示一份草稿：
- 要加进
CLAUDE.md/AGENTS.md（哪一个被编辑见第 4 步的选择规则）的## Agent skills块 docs/agents/issue-tracker.md和docs/agents/triage-labels.md（最后一个只在triage已安装时）的内容
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.
- 3d ago First seen · 104 lines · 37 tokens per session scan A e38fb6500ce0
init_qoder_harness is a skill published in the GitHub repository astordu/qoderharness (21 stars, last pushed 7d ago), licensed MIT. It adds 37 tokens to every session and 1,596 once invoked, about $0.0002 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…