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/thomas-powers-jr/cadence/issue-trackergit clone --depth 1 https://github.com/thomas-powers-jr/cadenceWrote 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/thomas-powers-jr/cadence/issue-tracker)<a href="https://agentmods.dev/agents/thomas-powers-jr/cadence/issue-tracker"><img src="https://agentmods.dev/badge/agents/thomas-powers-jr/cadence/issue-tracker.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.00283 |
| Opus 5 | $0.00000 | $0.00142 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
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 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.
This is a copy
83% identical to issue-tracker — 4 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. 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.
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.
- 4d ago First seen · 23 lines · 0 tokens per session scan A f0e138631d1f
issue-tracker is an agent published in the GitHub repository thomas-powers-jr/cadence (2 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 283 tokens. A static security scan graded it A with 0 findings. It is 83% identical to issue-tracker, differing in 4 lines, and is treated as a copy.
Other agents, from other repositories
retro
After an initiative closes, reads the ledger, the notes and the agents' reports and improves Tyran itself - skills, agents, scripts and docs, never product code. Defends hard against bloat and overfitting, so the default answer is to change nothing.
evolve-triage
Cycle-scope triage agent for the Evolve Loop (v8.56.0+, Layer C; default-on as of v8.59.0). Sits between Scout and Plan-review on every cycle unless opted out via workflow.phaseenables.triage=off in policy.json. Reads the scout-report backlog plus carryoverTodos and decides topn[] for THIS cycle, deferred[] for next…
evolve-operator
Post-cycle monitoring agent for the Evolve Loop. Assesses progress, detects stalls, tracks quality trends, and recommends adjustments.
issue-triage
You are a specialized issue triage agent that analyzes GitHub issues and categorizes them for efficient prioritization.
master-planner
Stateful kernel controller for the plan tree. Owns plan persistence at .claude/plans/, dispatches replan decisions via failure-classifier, and audits every decision to history.jsonl. NEVER executes tasks directly — always delegates to specialist agents (architect, frontend, mobile, tester, security, devops).
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.