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/modernweb-dev/rocket/issue-trackergit clone --depth 1 https://github.com/modernweb-dev/rocketWhat 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.02156 |
| Opus 5 | $0.00000 | $0.01078 |
| Sonnet 5 | $0.00000 | $0.00431 |
| Haiku 4.5 | $0.00000 | $0.00216 |
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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker: Local Markdown
Issues and PRDs for this repo live as markdown files in .scratch/.
Conventions
- One feature per directory:
.scratch/<feature-slug>/ - The PRD is
.scratch/<feature-slug>/PRD.md - Implementation issues are
.scratch/<feature-slug>/issues/<NN>-<slug>.md, numbered from01 - Triage state is recorded as a
Status:line near the top of each issue file (seetriage-labels.mdfor the role strings) - Agent loop execution state is recorded as an
Agent state:line near the top of each issue file. - Agent working method is recorded as an optional
Workflow:line near the top of each issue file. - Comments and conversation history append to the bottom of the file under a
## Commentsheading
Example issue metadata:
# Issue Title
Status: ready-for-agent
Agent state: pending
Workflow: content
Type: AFK
Agent workflow
Workflow: selects how the automated agent should approach implementation. It does not change issue eligibility, Agent state:, or verification gates.
Allowed Workflow: values:
tdd- behavior and code changes. This is the default whenWorkflow:is missing.content- documentation, website copy, examples, navigation, and static content changes. The agent implements directly, does not force a red-green-refactor loop, and adds or updates tests only when they protect executable behavior or prevent a meaningful regression. The normal verification gates still run; content-specific checks such as docs builds, preview builds, link/path inspection, or screenshots are selected based on the touched surface and issue acceptance criteria.
The Workflow: field name is case-sensitive. Workflow values are trimmed and normalized to lowercase; write them lowercase in issue files. Multiple Workflow: lines or unknown workflow values are issue metadata errors and stop issue-loop planning. The workflow declared in the issue is the durable source of truth; the loop does not provide a CLI override in v1.
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 · 127 lines · 0 tokens per session scan A 20cf02de7ea6
issue-tracker is an agent published in the GitHub repository modernweb-dev/rocket (394 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,156 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
Agentic Workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.
Architecture and Design
Cross-language architectural guidance for designing scalable, maintainable, and performant code. Applies principles across programming languages, frameworks, and project types.
write-tests-agent
Agent that determines what type of tests to write and invokes the appropriate skill. Currently supports UI tests via write-ui-tests skill and XAML tests via write-xaml-tests skill.
GitHub Actions Engineer
Expert-level software engineering agent specialized in GitHub Actions, cross-repo orchestration, and robust workflow automation.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…