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/issue-trackergit 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.00140 |
| Opus 5 | $0.00000 | $0.00070 |
| Sonnet 5 | $0.00000 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
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 yesterday.
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
Issue tracker: GitHub
Issues and PRDs for this repository live in GitHub Issues. Use the gh CLI from this clone so the repository is inferred from origin.
Conventions
- Create issues with a concise outcome-oriented title and a body containing evidence, acceptance criteria, and dependencies.
- Read the issue body, labels, and comments before implementation.
- Use
gh issue listwith JSON output for triage and planning. - Comment with verification evidence before closing an issue.
- Apply the role labels mapped in
docs/agents/triage-labels.md. - Do not close an issue merely because a patch exists; close it when its acceptance criteria pass.
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.
- yesterday First seen · 13 lines · 0 tokens per session scan A 5aa37bad95e8
issue-tracker is an agent published in the GitHub repository SquareWaveSystems/squarebox (71 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 140 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
HANDOFF
State: verified locally — publication and external CI remain user-owned.
explore
Semantic codebase exploration using Context King protocol.
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
flutter-integration-analyzer
Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a server log and asks why a specific misbehavior occurred (e.g. "why did it stop responding"), this agent parses the log…
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
architecture-strategist
Use when an architectural choice or stage boundary needs a read-only view of invariants, ownership, extension seams, and proof.