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/issue-trackergit clone --depth 1 https://github.com/darecstowell/scratchboardWhat 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.00997 |
| Opus 5 | $0.00000 | $0.00498 |
| Sonnet 5 | $0.00000 | $0.00199 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
issue-tracker 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker: local markdown
Tickets for this repo live as markdown files in .scratch/, and the board bakes them to the
Pages demo on every push. The tickets are public copy.
Conventions
-
The
statusfield is the lane, and the folder carries nothing. Every folder under.scratch/is a piece of work, never a state. -
One ticket per file:
.scratch/<n>-<slug>.md, flat at the root.<n>is the next free number across the backlog. -
State lives in YAML frontmatter, not in the body:
--- title: Narrow the npm publish token to scratchboard alone status: ready-for-human priority: p0 labels: [security, release, ci] ---statusholds the triage role and places the card. Seetriage-labels.mdfor the strings. -
The body starts with an
# <title>heading and ends with a## Done whensection that a reader can verify. -
Comments and history append to the bottom under a
## Commentsheading.
Lane discipline
A ticket's status says where its work actually is, so moving a card means editing one line.
Nothing carries done that is not shipped and verifiable in the history. A ticket whose
status is a lie is a lie the demo tells on every page load.
The lanes are declared in scratchboard.json, one per value, in triage order. done and
wontfix are collapsed, because a terminal lane grows without bound and nobody reads it. The
board never writes status; an agent does, which is what "tickets are agent-driven, so the
agent moves the card" already says.
When a skill says "publish to the issue tracker"
Write a new file at .scratch/<n>-<slug>.md. Take the next free number, add the frontmatter
above with status: needs-triage, and give it a ## Done when section.
When a skill says "fetch the relevant ticket"
Read the file at the referenced path. The user usually gives the path or the ticket number. A
backlog ticket is .scratch/<n>-*.md; an effort's ticket is .scratch/<effort>/issues/<NN>-*.md
and numbers restart at 01 inside each effort, so the two can collide.
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 · 79 lines · 0 tokens per session scan A 145e8167ab3f
issue-tracker is an agent published in the GitHub repository darecstowell/scratchboard (6 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 997 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
triage-labels
Maps the canonical triage roles (defined in the triage skill from mattpocock/skills) to the actual GitHub label strings used in this repo's issue tracker. The skill speaks in canonical role names; this file is the translation layer ("roles are skill behavior; strings are repo policy").
code-reviewer
Review PRs against this checklist. Be concise - only comment on actual issues.
claude
Configure Claude Code as your AI coding agent.
codex
Configure OpenAI Codex as your AI coding agent.
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.
chorus-task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn via the blocking subagent tool after chorussubmitforverify.