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 agents/open-software-network/os-clovy/triage-labelsgit clone --depth 1 https://github.com/open-software-network/os-clovyWrote 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/agents/open-software-network/os-clovy/triage-labels)<a href="https://agentmods.dev/agents/open-software-network/os-clovy/triage-labels"><img src="https://agentmods.dev/badge/agents/open-software-network/os-clovy/triage-labels.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00248 |
| Opus 5 | $0.00000 | $0.00124 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
triage-labels 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 4d 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
Triage Labels
The skills speak in terms of five canonical triage roles. os-platform Issues have both statuses and labels; this repo maps roles across both axes.
| Role in mattpocock/skills | In our tracker | Meaning |
|---|---|---|
needs-triage |
label needs-triage |
Maintainer needs to evaluate |
needs-info |
label needs-info |
Waiting on reporter |
ready-for-agent |
status todo + description enriched by os-task-prep (diagnosis, files, acceptance, verify) |
Fully specified, AFK-ready |
ready-for-human |
label ready-for-human (status todo) |
Requires human implementation |
wontfix |
status cancelled |
Will not be actioned |
When a skill mentions a role (e.g. "apply the AFK-ready triage label"), use
this table. Status changes go through the documented status endpoint (or
issues take for todo → in_progress); label writes are undocumented — follow
the probe-then-verify rule in issue-tracker.md.
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.
- 4d ago First seen · 18 lines · 0 tokens per session scan A ba0582554e10
triage-labels is an agent published in the GitHub repository open-software-network/os-clovy (357 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 248 tokens. 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 agents, from other repositories
demo-agents
We need a steady flow of demo videos — X/Twitter, Reddit, YouTube Shorts, blog posts, App Store-style screen recordings — and we'd like to scale that without scheduling Daniel to record every clip by hand. This doc maps the content-creation agent landscape, names the gap between "synthetic video hype" and "scripted…
qa-agents
Every quarter someone pitches an "AI does QA" tool. Most are web-first or mobile-first. MacParakeet is a menu-bar macOS app with a non-activating KeylessPanel overlay, global dictation hotkeys, and TCC-gated microphone/screen-recording flows. The general AI-QA frontier doesn't speak our shape yet. This doc tracks…
flow-verifier
Runs the VZT Flow end-to-end verification ladder (build, tests, TTS-transcribe checks, clean-test latency, paste-test, daemon socket checks, overlay states) and reports real measured numbers — never estimates. Use before claiming a change works, before a release, or when asked to verify VZT Flow.
flow-feature-builder
Implements VZT Flow features observing this repo's boundaries — additive edits, the gotcha list from CLAUDE.md, pull-rebase discipline in a shared worktree, never touching the user's running daily-driver app without relaunching it. Use for routine feature/bugfix work in this repo.
ai-systems-architect
Use as the cross-cutting AI/systems DESIGN authority to decide WHERE a seam goes across the Rust core, Angular FE, and brain — provider/model abstraction, agentic tool-use loop bounds, tool/ACI design, the egress-consent-redaction-ledger firewall, routing, context assembly, a new ingest source or consumption surface.…
adversarial-verifier
Anti-false-positive verifier for Murmur. Use AFTER a change is written, to TRY TO BREAK it — run the real gates (cargo test --lib / ng build / ng lint), live-reproduce in a browser against the zoneless Angular app with a mocked Tauri IPC, and hunt for the failure modes this app has actually shipped (sealed-content…