issue-tracker

issue-tracker is a skill for Claude Code, Codex from Community-Access/accessibility-agents. It costs 21 tokens per session (1,453 once invoked), scanned A, original, MIT.

A GitHub issue management assistant for finding, reviewing, and organizing issues. GitHub issues are discussion and work-tracking records attached to code repositories.

In plain words
What is it for?
Searching issues, investigating full threads, building triage dashboards, tracking linked pull requests, and creating Markdown and HTML reports in the workspace.
Why use it?
It brings issue threads, comments, reactions, releases, and related discussions together so work can be triaged with more context.

Skill for Claude CodeCodex

Written for Claude Code and Codex: disable-model-invocation in frontmatter, but also agents/openai.yaml present.

Part of the accessibility-agents plugin — 108 skills, 6 hooks shipped together

Good fit Searching issues, investigating full threads, building triage dashboards, tracking linked pull requests, and creating Markdown and HTML reports in the workspace.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/community-access/accessibility-agents/issue-tracker
Install

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.

Any agent
npx skills add Community-Access/accessibility-agents --skill issue-tracker
Clone the repo
git clone --depth 1 https://github.com/Community-Access/accessibility-agents

Made for: Claude Code, Codex.

Or install accessibility-agents, the plugin that ships this one along with the rest of its 108 skills, 6 hooks.

Wrote 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.

agentmods badge for issue-tracker

README.md
[![agentmods](https://agentmods.dev/badge/skills/community-access/accessibility-agents/issue-tracker/github.svg)](https://agentmods.dev/skills/community-access/accessibility-agents/issue-tracker)
Your own site
<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/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for issue-tracker

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,453 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 10 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Prompt Injection · line 236
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
  • high Prompt Injection · line 285
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
  • medium Agent Snooping · line 10
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Agent Snooping · line 10
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Agent Snooping · line 10
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Agent Snooping · line 10
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Agent Snooping · line 10
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Excessive Agency · line 729
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Excessive Agency · line 732
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • low Excessive Agency · line 114
    Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.
    Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.01453
Opus 5.5 $0.00008 $0.00581
Sonnet 5.5 $0.00004 $0.00291
Haiku 4.5 $0.00002 $0.00145

Measured 1mo ago against content hash e796499d5b38, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

skills/issue-tracker/SKILL.md · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Issue Tracker Agent

Shared instructions

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.

Intelligence Layer

Priority Scoring

Internally score each issue when listing:

  • +3: User was @mentioned and hasn't responded
  • +3: Tied to an upcoming release milestone
  • +2: P0, P1, critical, urgent, blocker label
  • +2: New comments from others since user's last comment
  • +2: High community interest (5+ positive reactions)
  • +1: bug label
  • +1: Assigned to user
  • +1: Has active related discussion
  • -1: wontfix, duplicate, question label
  • -2: No activity >30 days

Sort by score descending. Show the signal column based on this.

Smart Action Item Inference

When generating documents, analyze the conversation to create action items:

  • If the last comment is a question directed at the user --> "Respond to @X's question about {topic}"
  • If the issue has a needs-info label --> "Provide requested information about {topic}"
  • If the issue is stale and assigned to user --> "Update status or close -- no activity for {N} days"
  • If a PR is linked and merged --> "Verify fix and close issue -- PR #N: Title was merged on {date}"
  • If tests or repro steps were requested --> "Add test case / reproduction steps"
  • If the issue has high community interest --> "Consider prioritizing -- {N} community reactions"
  • If a discussion thread is active --> "Check Discussion: Title for related context"
  • If a release is approaching --> "Release v{X} includes this -- verify before deadline"

Read the full file on GitHub · 147 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 1mo ago Changed · -590 lines · -21 tokens per session e796499d5b38
  2. 1mo ago First seen · 737 lines · 42 tokens per session scan A 381576c9ba40

Subscribe to this mod's changes

issue-tracker is a skill published in the GitHub repository Community-Access/accessibility-agents (429 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 1,453 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

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…

ericrisco/rsc-harness · 86 tokens

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.

PramodDutta/qaskills · 32 tokens

Accessibility A11y Enhanced

Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.

PramodDutta/qaskills · 34 tokens

accessibility-commerce

Make your store usable by everyone with WCAG 2.1 AA compliance — screen reader support, keyboard navigation, and accessible cart and checkout flows.

finsilabs/awesome-ecommerce-skills · 33 tokens

accessibility-expert

Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or…

personamanagmentlayer/pcl · 98 tokens

monochrome

Build accessible UI with monochrome, the framework-agnostic UI library for agents. Use whenever a project depends on monochrome or has ids starting with mct:, mcc:, or mcr:, and whenever you write or fix an accordion, collapsible, dialog or modal, dropdown or context menu, menubar, popover, tabs, or tooltip in HTML…

vaneenige/monochrome-ui · 97 tokens