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 astordu/qoderharness --skill triagegit 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/triage)<a href="https://agentmods.dev/skills/astordu/qoderharness/triage"><img src="https://agentmods.dev/badge/skills/astordu/qoderharness/triage/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/astordu/qoderharness/triage"><img src="https://agentmods.dev/badge/skills/astordu/qoderharness/triage.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.00051 | $0.01880 |
| Opus 5.5 | $0.00020 | $0.00752 |
| Sonnet 5.5 | $0.00010 | $0.00376 |
| Haiku 4.5 | $0.00005 | $0.00188 |
Grade A, and why
triage 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 1mo 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
分诊（Triage）
分诊的核心职责是驱动 issue tracker 上的每个 issue 流经一个小型状态机——由多个分诊角色依次完成分类、验证与流转。
如果本仓库将外部 pull request 也纳入请求来源（详见 issue-tracker 配置），分诊流程同样适用于 PR。可以把 PR 理解为"附带代码变更的 issue"：它复用相同的角色、状态和状态机，仅在少数环节存在针对 PR 的特殊处理（详见下文）。至于裸编号 #42 究竟指向 issue 还是 PR，由 tracker 配置决定。
分诊期间发布到 issue tracker 的每一条评论或 issue 都必须 以这条免责声明开头：
> *This was generated by AI during triage.*
参考文档
- AGENT-BRIEF.md — 如何撰写经久耐用的 agent 简报
- OUT-OF-SCOPE.md —
.out-of-scope/知识库如何运作
角色
两个 分类（category） 角色：
bug— 有东西坏了enhancement— 新功能或改进
五个 状态（state） 角色：
needs-triage— 维护者需要评估needs-info— 等待报告者提供更多信息ready-for-agent— 已完全明确，可交给一个离线（AFK）agentready-for-human— 需要人来实现wontfix— 不会处理
对 PR 而言，这些相同的状态是对照附带的代码来理解的：ready-for-agent 表示已附上一份简报、应由一个 agent 对该 diff 走下一步；ready-for-human 表示已准备好供人来合并。
每个经过分诊的 issue 都应恰好带有一个分类角色和一个状态角色。如果状态角色之间相互冲突，就把它标出来，并在做任何其他事情之前询问维护者。
这些是规范角色名——issue tracker 中实际使用的标签字符串可能不同。这个映射应当已经提供给你——如果没有，运行 /init_goder_harness。
状态转换：一个未打标签的 issue 通常先进入 needs-triage；从那里它转向 needs-info、ready-for-agent、ready-for-human 或 wontfix。一旦报告者回复，needs-info 就回到 needs-triage。维护者可以随时覆盖——把看起来不寻常的转换标出来，并在继续之前询问。
调用方式
维护者调用 /triage 并用自然语言描述他们想要什么。解读这个请求并采取行动。例如：
- "给我看看任何需要我关注的东西"
- "咱们来看看 #42"（issue 或 PR）
- "把 #42 移到 ready-for-agent"
- "有什么已经准备好可供 agent 领取的？"
展示需要关注的东西
查询 issue tracker，并呈现三个桶，最旧的在前：
- Unlabeled（未打标签）——从未被分诊过。
needs-triage——评估进行中。needs-info且自上次分诊笔记以来报告者有活动——需要重新评估。
当 PR 在范围内时，把外部 PR 也纳入这些桶，并给每一行标记 [PR] 或 [issue]。发现（discovery）只浮现 外部 PR（tracker 配置定义了谁算外部）——一位协作者进行中的 PR 不是分诊工作。这个过滤只用于发现；一个被明确点名的 PR 无论作者是谁都始终会被分诊。
展示计数以及每一项的一行摘要。让维护者来挑。
分诊某个具体的 issue 或 PR
-
收集上下文。 阅读完整的 issue 或 PR（正文、评论、标签、作者、日期；对 PR 还要看 diff）。解析任何先前的分诊笔记，以免重复追问已解决的问题。使用项目的领域词汇表探索代码库，并尊重该区域内的 ADR。对代码库跑两项检查：(a) 冗余——按领域概念（不只是请求的字面措辞）搜索所请求行为是否已有实现，并报告你查过哪些地方。如果找到了，那就是一个已实现的
wontfix（第 5 步）。(b) 先前否决——阅读.out-of-scope/*.md，浮现任何与此请求相似的记录。 -
给出建议。 把你的分类与状态建议连同理由告诉维护者，外加一段与该请求相关的简短代码库摘要——包括它是否已被实现。等待指示。
What ships with it
2 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.
- 1mo ago First seen · 113 lines · 51 tokens per session scan A 6099d61c6016
triage is a skill published in the GitHub repository astordu/qoderharness (38 stars, last pushed 23d ago), licensed MIT. It adds 51 tokens to every session and 1,880 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.