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/darecstowell/scratchboard/triage-labelsgit clone --depth 1 https://github.com/darecstowell/scratchboardWrote 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/darecstowell/scratchboard/triage-labels)<a href="https://agentmods.dev/agents/darecstowell/scratchboard/triage-labels"><img src="https://agentmods.dev/badge/agents/darecstowell/scratchboard/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.00534 |
| Opus 5 | $0.00000 | $0.00267 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00053 |
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 five canonical triage roles. This file maps those roles to the strings this
repo uses. A ticket carries its role in the status field of its frontmatter.
| Label in mattpocock/skills | Label in our tracker | Meaning |
|---|---|---|
needs-triage |
needs-triage |
Maintainer needs to evaluate this ticket |
needs-info |
needs-info |
Waiting on the reporter for information |
ready-for-agent |
ready-for-agent |
Fully specified, ready for an AFK agent |
ready-for-human |
ready-for-human |
Needs a human to implement it |
wontfix |
wontfix |
Will not be actioned |
| none | done |
Shipped and verifiable in the history |
When a skill names a role, for example "apply the AFK-ready triage label", write the string from
the right-hand column into the ticket's status field.
done is scratchboard's own, and upstream has no equivalent: the five roles are a triage queue,
not a lifecycle, and on a real tracker "done" is the issue being closed. An agent writes it, and
skills/scratchboard/SKILL.md teaches that. The board never does, because read-only holds.
status is also the lane. There is no second axis: the folder carries nothing, so the field
says both how ready a ticket is and where the card sits.
Edit the right-hand column to change the vocabulary.
scratchboard.json declares one lane per value in this table, and one more for deferred.
deferred is not in the table because it is not a triage role and not in the published spec. It
means "someone looked and chose later", which needs-triage loses, so it survives as this repo's
own value. A stranger's unrecognized value behaves the same way: it passes through untouched and
takes its lane from local config.
Name the sixth lifecycle state
settled done, and
Migrate this repo's own board to triage-role lanes
made the config match.
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 · 37 lines · 0 tokens per session scan A c7ebc1f45f03
triage-labels is an agent published in the GitHub repository darecstowell/scratchboard (6 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 534 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-31.
Other agents, from other repositories
chorus-proposal-reviewer
Review submitted Chorus proposals for quality — check document completeness, task granularity, AC alignment, and cross-task dependencies. Spawn via the blocking subagent tool after choruspmsubmitproposal.
task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn after chorussubmitforverify.
daily-standup
Daily automated standup with WhatsApp delivery to two groups (Executive + Motivational).
github-issue-gc
Autonomous GitHub issue quality assurance - detect stale, invalid.
forge
Universal forge orchestrator - breaks wishes into execution groups with task files and validation (all domains).
Issue Creator
I create GitHub issues intelligently by analyzing commits, diffs, or natural language descriptions.