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 wangmiaozero/pi-harness --skill triagegit clone --depth 1 https://github.com/wangmiaozero/pi-harnessWrote 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/wangmiaozero/pi-harness/triage)<a href="https://agentmods.dev/skills/wangmiaozero/pi-harness/triage"><img src="https://agentmods.dev/badge/skills/wangmiaozero/pi-harness/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/wangmiaozero/pi-harness/triage"><img src="https://agentmods.dev/badge/skills/wangmiaozero/pi-harness/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.00033 | $0.01556 |
| Opus 5 | $0.00016 | $0.00778 |
| Sonnet 5 | $0.00007 | $0.00311 |
| Haiku 4.5 | $0.00003 | $0.00156 |
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 11d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What ships with it
3 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.
- 11d ago First seen · 113 lines · 33 tokens per session scan A 623a2ed692bd
triage is a skill published in the GitHub repository wangmiaozero/pi-harness (58 stars, last pushed 3d ago), licensed AGPL-3.0. It adds 33 tokens to every session and 1,556 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
ce:work
Execute work plans efficiently while maintaining quality and finishing features.
file-todos
This skill should be used when managing the file-based todo tracking system in the .context/compound-engineering/todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with code review processes.
triage
Triage and categorize findings for the CLI todo system.
resolve-todo-parallel
Resolve all pending CLI todos using parallel processing, compound on lessons learned, then clean up completed todos.
to-issues
A workflow that turns a product requirements document (PRD) or technical specification (SPEC) into small, actionable work tickets.
fabric-swarm
Creates a self-organizing team of persistent Pi Fabric actors with durable topics, mailboxes, and compare-and-swap tasks. Use for messenger-like collaboration and long-lived delegated work.