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/squarewavesystems/squarebox/triage-labelsgit clone --depth 1 https://github.com/SquareWaveSystems/squareboxWhat 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.00133 |
| Opus 5 | $0.00000 | $0.00067 |
| Sonnet 5 | $0.00000 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00013 |
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 2d 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
| Canonical role | GitHub label | Meaning |
|---|---|---|
needs-triage |
needs-triage |
Maintainer needs to evaluate the issue |
needs-info |
needs-info |
Waiting for reporter information |
ready-for-agent |
ready-for-agent |
Fully specified and safe for an AFK agent |
ready-for-human |
ready-for-human |
Requires human implementation or judgment |
wontfix |
wontfix |
Will not be actioned |
All canonical role labels are configured in GitHub.
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.
- 2d ago First seen · 12 lines · 0 tokens per session scan A 1070d9c755af
triage-labels is an agent published in the GitHub repository SquareWaveSystems/squarebox (71 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 133 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
sprint-master
Agile delivery partner for sprint planning, retrospectives, velocity analysis, and user stories. Use when planning a sprint, running a retro, estimating capacity, or breaking epics into stories. Uses the capacity calculator to size commitments.
shepherd
OSS shepherd, Python/ML/CV/AI — contributor communication (triage, reply/PR drafts), release coordination (SemVer, PyPI, CHANGELOG). NOT for docstrings/README (foundry:doc-scribe), CI/publish YAML (oss:cicd-steward), diff review (/oss:review), CHANGELOG gen (/oss:release). TRIGGER: triaging issues/PRs, SemVer. SKIP…
task-tree-triage
Cheap per-issue classifier for recursive task planning. Reads one GitHub issue, checks task-tree markers, and returns whether to skip, mark as an implementation-ready leaf with executor routing, or send to the smart planner for subtask expansion.
projects
A project bundles a folder with its defaults. One project = 1 folder + defaults + pinned sessions + a display name and icon. Sessions belong to a project; the project's folder is the cwd the agent subprocess runs in.
Technical Manager
Engineering manager that coordinates all agents, tracks progress, prioritizes work, and surfaces decisions to the human operator.
issue-tracker
Issues and specs for this repo live as GitHub issues. Use the gh CLI for all operations.