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/brettkinny/dotty-stackchan/issue-trackergit clone --depth 1 https://github.com/BrettKinny/dotty-stackchanWhat 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.00504 |
| Opus 5 | $0.00000 | $0.00252 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00050 |
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.
This is a copy
88% identical to issue-tracker — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Issue tracker: GitHub
Issues and PRDs for this repo live as GitHub issues on BrettKinny/dotty-stackchan. Use the gh CLI for all operations.
Conventions
- Create an issue:
gh issue create --title "..." --body "...". Use a heredoc for multi-line bodies. - Read an issue:
gh issue view <number> --comments, filtering comments byjqand also fetching labels. - List issues:
gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]'with appropriate--labeland--statefilters. - Comment on an issue:
gh issue comment <number> --body "..." - Apply / remove labels:
gh issue edit <number> --add-label "..."/--remove-label "..." - Close:
gh issue close <number> --comment "..."
Infer the repo from git remote -v — gh does this automatically when run inside a clone. Note this clone has two remotes: origin → BrettKinny/dotty-stackchan (the canonical repo) and fork → pboushy/dotty-stackchan. Target origin unless told otherwise (e.g. gh issue list --repo BrettKinny/dotty-stackchan).
Existing label conventions
This repo already uses workflow labels that the triage labels complement, not replace:
status:active,status:bench-pending,status:blocked,status:speculative— lifecycle state (see thedotty-task-runnerskill).area:firmware,area:bridge,area:xiaozhi,area:dashboard,area:infra,area:docs,area:behaviour— which part of the stack.safety— child-safety / correctness bug.
Keep applying these alongside the triage roles in docs/agents/triage-labels.md.
When a skill says "publish to the issue tracker"
Create a GitHub issue.
When a skill says "fetch the relevant ticket"
Run gh issue view <number> --comments.
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 · 33 lines · 0 tokens per session scan A 3407d0ab676d
issue-tracker is an agent published in the GitHub repository BrettKinny/dotty-stackchan (105 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 504 tokens. A static security scan graded it A with 0 findings. It is 88% identical to issue-tracker, differing in 18 lines, and is treated as a copy.
Other agents, from other repositories
debugger
Use when something is broken and the cause isn't obvious — bugs, error stack traces, "works in dev not prod", performance regressions, weird behavior after a change.
reviewer
Use to review code changes (diffs, PRs, single files) for bugs, security issues, performance problems, style violations, and missing edge cases. Read-only — produces a review, doesn't fix code.
researcher
Use for any task requiring external research — finding documentation, comparing libraries, looking up release notes, market research, fact-checking. Read-only by design — won't modify files. Auto-delegate when query starts with "find", "research", "look up", "compare", "what is the latest".
tester
Use to write, run, or debug tests. Auto-discovers test framework (pytest, jest, vitest, go test, cargo test). Invoke after implementing a feature that needs coverage, or when tests are failing.
WEBHOOK_SDK
Write a custom Commonly agent in 30 lines of Python. The SDK is a single stdlib-only file that implements the four CAP verbs; the scaffolder wires publish + install + token-issuance in one command.
Reviewer
Use when: reviewing C++ code for quality, checking memory safety and RAII compliance, verifying cross-platform portability, enforcing API consistency, reviewing for thread safety, checking const-correctness, auditing error handling patterns.