agentmods.dev

issue-track

issue-track is a command for Claude Code from C0ntr0lledCha0s/claude-code-plugin-automations. It costs 17 tokens per session (2,596 once invoked), scanned A, original, MIT.

A command for synchronizing open GitHub issues—tracked work items in a software project—and showing them as local tasks.

In plain words
What is it for?
Use it to list, filter, sync, select, or clear GitHub issues by assignment, labels, milestones, projects, branch, or scope.
Why use it?
It keeps issue information available while you work and connects selected issues with commits without repeatedly looking them up.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the github-workflows plugin — 8 skills, 9 commands, 4 agents shipped together

not rated 3 6mo ago A scan 17 tokens original MIT
View the source file C0ntr0lledCha0s/claude-code-plugin-automations
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.

agentmods
npx agentmods add commands/c0ntr0lledcha0s/claude-code-plugin-automations/issue-track
Clone the repo
git clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automations

Made for: Claude Code.

Or install github-workflows, the plugin that ships this one along with the rest of its 8 skills, 9 commands, 4 agents.

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-track

README.md
[![agentmods](https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/issue-track.svg)](https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/issue-track)
Your own site
<a href="https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/issue-track"><img src="https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/issue-track.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,596 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00017 $0.02596
Opus 5 $0.00009 $0.01298
Sonnet 5 $0.00003 $0.00519
Haiku 4.5 $0.00002 $0.00260

Measured 6d ago against content hash 6d3bc9274fbe, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

issue-track 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 6d 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.

github-workflows/commands/issue-track.md · 319 lines

How it starts

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

Issue Track

Synchronize GitHub issues to a local cache and display them as trackable tasks. This enables automatic issue references in commits.

Usage

/issue-track                    # Show cached issues (uses cache if fresh, syncs if stale/empty)
/issue-track sync               # Force sync from GitHub, bypassing cache
/issue-track assigned           # Sync issues assigned to you
/issue-track labeled priority:high  # Sync issues with specific label
/issue-track milestone "Sprint 5"   # Sync issues in milestone
/issue-track project "Agent Plugin Development"  # Sync issues in project board (by title)
/issue-track project 3          # Sync issues in project board (by number)
/issue-track all                # Sync all open issues
/issue-track context            # Show issues filtered by context (project + scope + assignment)
/issue-track scope              # Show issues matching branch scope
/issue-track branch             # Show only issues selected for current branch
/issue-track select 42 43       # Select issues for current branch
/issue-track clear              # Clear the local cache

Arguments

  • First argument (optional): Filter type or action

    • sync: Force sync from GitHub, bypassing cache
    • assigned: Issues assigned to current user
    • labeled: Issues with specific label (requires second arg)
    • milestone: Issues in specific milestone (requires second arg)
    • project: Issues in specific project board (requires second arg: title or number)
    • all: All open issues in repository
    • context: Show issues filtered by combined context (project + scope + assignment)
    • scope: Show issues matching the branch's detected scope label
    • branch: Show only issues selected for the current branch
    • select: Select issues for current branch (requires issue numbers as additional args)
    • clear: Clear the local cache
    • (empty): Show cached issues if fresh (< 15 min old), otherwise sync using default filter

  • Second argument (optional): Filter value for labeled, milestone, project, or select

    • For project: Can be project title (string) or project number (integer)
    • For select: One or more issue numbers (e.g., select 42 43 44)

Read the full file on GitHub · 319 lines

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. 6d ago First seen · 319 lines · 17 tokens per session scan A 6d3bc9274fbe

Subscribe to this mod's changes

issue-track is a command published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 2,596 once invoked, about $0.0001 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-31.

Project management
Related

Other commands, from other repositories

template

Manage issue templates for streamlined issue creation.

gastownhall/beads · 0 tokens

sync-linear

Sync current work with Linear ticket status.

bybren-llc/safe-agentic-workflow · 0 tokens

add-note

Add an internal or external note to a ConnectWise PSA ticket.

WYRE-AI/msp-claude-plugins · 12 tokens

fest-show

Show festival progression (in-progress tasks, roadmap, and dependency view).

Obedience-Corp/festival · 17 tokens

dispatcher

Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.

Kanevry/session-orchestrator · 0 tokens

workpm

PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.

Dannykkh/skill-olympus · 31 tokens