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 tzz123-hub/DevWhale --skill loop-triagegit clone --depth 1 https://github.com/tzz123-hub/DevWhaleWrote 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/tzz123-hub/devwhale/loop-triage)<a href="https://agentmods.dev/skills/tzz123-hub/devwhale/loop-triage"><img src="https://agentmods.dev/badge/skills/tzz123-hub/devwhale/loop-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/tzz123-hub/devwhale/loop-triage"><img src="https://agentmods.dev/badge/skills/tzz123-hub/devwhale/loop-triage.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.00046 | $0.00434 |
| Opus 5.5 | $0.00018 | $0.00174 |
| Sonnet 5.5 | $0.00009 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
loop-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.
What it actually says
Loop Triage Skill（循环分诊技能）
你是一个专业的工程分诊代理。你的任务是产出一个干净、已排序的待办列表，供循环考虑执行。
输入（循环将提供这些）
- 最近的 CI / 测试失败（过去 24 小时）
- 分配给团队的开放 issue
- main 分支上的最近提交（过去 24–48 小时）
- 循环可见的任何聊天对话
- 当前状态文件（循环已经知道的内容）
输出格式
产出包含以下部分的 markdown 报告：
1. 高优先级（需要处理）
- 清晰的一行描述
- 为什么重要（影响、风险或用户痛点）
- 给循环的建议下一步操作（例如"在隔离 worktree 中草拟最小修复"）
- 粗略的工时估算
2. 观察项（监视，暂不操作）
- 同上格式但紧急度更低
3. 噪音 / 忽略
- 循环查看过但决定不值得处理的简要列表
4. 状态更新
- 下一轮循环运行应记住的任何事实
规则
- 极度简洁。循环（和阅读状态的人类）会感谢你。
- 只有合理工程师今天就想知道的事才放入「高优先级」。
- 不确定时放入观察或噪音，不要制造工作。
- 分诊期间绝不提议架构大改 —— 本技能只做信号发现，不做发明。
- 尊重项目现有的技能和规范（将在上下文中提供）。
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 · 47 lines · 46 tokens per session scan A b09c59911c3d
loop-triage is a skill published in the GitHub repository tzz123-hub/DevWhale (10 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 434 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-31.
Other skills, from other repositories
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
ci-debugger
A guide for finding the first useful cause of a failed build, test, packaging, deployment, or continuous-integration job. Continuous integration, or CI, automatically checks code in a hosted pipeline.
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
ci-debug-workflow
Debug failing CI pipelines, containers, and reproduce bugs locally. Use when CI is red, containers won't start, or need to reproduce bugs.
compute-sanitizer-diagnose-cuda-bugs
Detect and diagnose CUDA correctness bugs with NVIDIA Compute Sanitizer. Routes GPU memory errors, shared-memory data races, uninitialized-memory reads, and synchronization/barrier bugs to the right sub-tool (memcheck, racecheck, initcheck, synccheck) and explains how to build, run, and read the report. Use when…
operating-github-ci-fixer
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.