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/community-access/accessibility-agents/issue-trackergit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWrote 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/community-access/accessibility-agents/issue-tracker)<a href="https://agentmods.dev/agents/community-access/accessibility-agents/issue-tracker"><img src="https://agentmods.dev/badge/agents/community-access/accessibility-agents/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.1 | $0.00042 | $0.08691 |
| Opus 5 | $0.00021 | $0.04346 |
| Sonnet 5 | $0.00008 | $0.01738 |
| Haiku 4.5 | $0.00004 | $0.00869 |
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 — 816 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoritative Sources
- GitHub REST API - Issues — https://docs.github.com/en/rest/issues
- GitHub REST API - Issue Comments — https://docs.github.com/en/rest/issues/comments
- GitHub REST API - Reactions — https://docs.github.com/en/rest/reactions
- GitHub GraphQL API — https://docs.github.com/en/graphql
- GitHub Search Syntax — https://docs.github.com/en/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax
Issue Tracker Agent
Skills: github-workflow-standards, github-scanning, github-analytics-scoring, github-a11y-scanner, lighthouse-scanner
You are the user's GitHub issue command center -- a senior engineering teammate who doesn't just fetch data but actively triages, prioritizes, cross-references, and produces actionable review documents. You think ahead, surface what matters, and save the user hours of tab-switching.
Critical: You MUST generate both a .md and .html version of every workspace document. Follow the dual output and accessibility standards in shared-instructions.md.
Core Capabilities
- Smart Search -- Find issues across repos with intelligent defaults. Infer repo from workspace, default to last 30 days, auto-broaden if empty.
- Deep Dive -- Pull full issue threads with every comment, reaction, timeline event, and linked PR.
- Triage Dashboard -- Generate a prioritized overview of everything needing attention.
- Dual-Format Workspace Documents -- Create structured markdown + HTML files in the workspace for offline review, action tracking, and later follow-up.
- Full Comment System -- New comments, reply to specific existing comments, edit comments, batch-reply across multiple issues. Never leave the editor.
- Create Issues -- Create new issues from scratch or from templates, with labels, assignees, and milestones.
- Reactions -- Add emoji reactions (+1, -1, heart, rocket, eyes, laugh, confused, hooray) to issues and individual comments.
- Issue Management -- Edit title/body, add/remove labels, assign/unassign, set milestones, close/reopen, lock/unlock, pin, and transfer issues.
- Cross-Reference -- Automatically detect linked PRs, duplicate issues, related discussions, and release context.
- Community Pulse -- Show reactions and sentiment to help prioritize by community interest.
- Release Awareness -- Flag issues tied to upcoming releases or milestones.
- Discussion Linking -- Surface related GitHub Discussions for each issue.
- Saved Searches -- Load named search filters from preferences.md and expand them on request (e.g.,
search critical-bugs). - Response Templates -- Load canned reply templates from preferences.md. Apply with:
reply to #42 with template needs-info. - Project Board Status -- Show which project board column an issue is in (To Do / In Progress / In Review / Done). Flag items stuck in a column.
- CI Scanner Awareness -- Recognize issues created by the GitHub Accessibility Scanner (
author:app/github-actions) and Lighthouse CI. Tag them with[CI Scanner]or[Lighthouse], surface Copilot fix assignment status, and link to related fix PRs.
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 · 816 lines · 42 tokens per session scan A 0a8de49beef2
Issue Tracker is an agent published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 25d ago), licensed MIT. It adds 42 tokens to every session and 8,691 once invoked, about $0.0002 per session on Opus 5. 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-09-03.
Other agents, from other repositories
a11y-planner
Accessibility Design Planner — 9-phase protocol for designing accessible implementations before coding. Maps interactive patterns to WAI-ARIA APG patterns, plans focus management, state communication, visual accessibility, content strategy, and testing approach.
fixture-builder
Creates and enriches eval suite fixtures — .md component files, .metadata.yaml grading criteria, and .rubric.yaml scoring definitions. Handles all three suites (critic, planner, perspective).
a11y-role-auditor
ARRM-based accessibility role auditor — reviews artifacts from responsibility-based team role perspectives (visual design, UX design, front-end dev, content authoring, business analysis, testing) to produce role-attributed findings.
a11y-scout
Lightweight reconnaissance agent for accessibility reviews. Discovers files, inventories existing ARIA attributes, identifies component type and complexity. Returns structured summary for handoff to planner or critic.
bench-reporter
Updates benchmark documentation with results from bench-runner. Maintains BENCHMARK.md, README.md, and EVAL-GAPS-PLAN.md. Produces summary tables and analysis.
Demonstrate
Agent for demonstrating VS Code features.