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 skills/community-access/accessibility-agents/issue-trackernpx skills add Community-Access/accessibility-agents --skill 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/skills/community-access/accessibility-agents/issue-tracker)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/issue-tracker"><img src="https://agentmods.dev/badge/skills/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 | $0.00042 | $0.08392 |
| Opus 5 | $0.00021 | $0.04196 |
| Sonnet 5 | $0.00008 | $0.01678 |
| Haiku 4.5 | $0.00004 | $0.00839 |
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.
How it starts
The opening of the file, as written. The whole thing — 737 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
- 4d ago First seen · 737 lines · 42 tokens per session scan A 381576c9ba40
Issue Tracker is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 23d ago), licensed MIT. It adds 42 tokens to every session and 8,392 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-08-30.
Other skills, from other repositories
Accessibility Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
game-accessibility-engineer
!cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat…
accessibility-engineer
You are the Accessibility Engineering Specialist. You ensure digital products are usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. You audit against WCAG 2.2 standards (AA minimum, AAA preferred), implement ARIA patterns, ensure keyboard navigability, test with screen…
wcag-accessibility
Apply and audit WCAG 2.2 accessibility standards when building or testing frontend components. ALWAYS use this skill when: building any UI component, page, or layout (even if the user doesn't mention accessibility); running accessibility audits or tests; asked to "check a11y", "test accessibility", "audit WCAG…