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 kraulerson/solo-orchestrator --skill sweep-triagegit clone --depth 1 https://github.com/kraulerson/solo-orchestratorWrote 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/kraulerson/solo-orchestrator/sweep-triage)<a href="https://agentmods.dev/skills/kraulerson/solo-orchestrator/sweep-triage"><img src="https://agentmods.dev/badge/skills/kraulerson/solo-orchestrator/sweep-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/kraulerson/solo-orchestrator/sweep-triage"><img src="https://agentmods.dev/badge/skills/kraulerson/solo-orchestrator/sweep-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.00063 | $0.02092 |
| Opus 5 | $0.00032 | $0.01046 |
| Sonnet 5 | $0.00013 | $0.00418 |
| Haiku 4.5 | $0.00006 | $0.00209 |
Grade A, and why
sweep-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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sweep Triage
What this is. A skill for consolidating findings from a sweep into one decision-grade document. A sweep is any activity that surfaces multiple findings at once: a multi-agent UAT run, a manual audit pass, a security review, a calibration replay. Each finding needs severity, a fix recommendation, and the whole set needs an overall ship recommendation.
What this is NOT. This skill is not for per-issue triage in an issue tracker (working through GitHub Issues or Linear one at a time, applying state-machine labels). That is a different workflow. If you want issue-tracker triage, see the related work below.
Canonical example.
Reports/uat-2026-04-29-bl029-validation/TRIAGE.md(committed to this repo) is the output shape this skill produces. Read it before writing your first TRIAGE — it shows the per-agent verdict table, severity-ranked issue list, and the Resolution section appended after fixes shipped.
When to use
- A multi-agent UAT sweep just finished and you have N agent reports in
Reports/<sweep-id>/results/agent-*.json. - A manual audit (security review, accessibility pass, code review) produced multiple findings.
- A calibration replay (cf. BL-029 / BL-030 work) produced verdicts across scenarios and personas.
- You're about to make a ship / no-ship decision and have more than 2-3 findings to weigh.
When NOT to use
- Single-finding issues — write the fix or file the BL item directly.
- Per-issue triage in an issue tracker — that's a different workflow (state machine + labels, not severity tiers + ship decisions). See Related work below.
- Trivial sweeps (everything green, no findings) — no document needed; the green test output is the artifact.
Output
The skill produces a markdown document at:
Reports/<sweep-id>/TRIAGE.md
Where <sweep-id> is the directory the sweep already lives in (e.g., uat-2026-04-29-bl029-validation). If there is no sweep directory yet, create one at Reports/<sweep-id>/ first.
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 · 108 lines · 63 tokens per session scan A 96695ef5abf6
sweep-triage is a skill published in the GitHub repository kraulerson/solo-orchestrator (29 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 2,092 once invoked, about $0.0003 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…