What is issue-tracker?

A set of rules for using GitHub as the project’s issue tracker, where issues record bugs, tasks, and product requirements.

Use it when handling repository issues, product requirement documents, labels, comments, or issue-related requests.

It gives the agent one consistent way to create, read, search, comment on, label, and close GitHub issues using the gh command-line tool.

issue-tracker — Agent for Claude Code by vipzhengmingming: A set of rules for using GitHub as the…

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 agents/vipzhengmingming/oh-my-powers/issue-tracker

Clone the repo

git clone --depth 1 https://github.com/vipzhengmingming/oh-my-powers

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/vipzhengmingming/oh-my-powers/issue-tracker.svg)](https://agentmods.dev/agents/vipzhengmingming/oh-my-powers/issue-tracker)

Your own site

<a href="https://agentmods.dev/agents/vipzhengmingming/oh-my-powers/issue-tracker"><img src="https://agentmods.dev/badge/agents/vipzhengmingming/oh-my-powers/issue-tracker.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 788 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 89% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00788
Opus 5	$0.00000	$0.00394
Sonnet 5	$0.00000	$0.00158
Haiku 4.5	$0.00000	$0.00079

Measured 5d ago against content hash 76ab60895910, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, 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 5d 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.

Origin

This is a copy

89% identical to issue-tracker — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

docs/agents/issue-tracker.md · 38 lines

How it starts

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

Issue tracker: GitHub

Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.

Conventions

Create an issue: gh issue create --title "..." --body "...". Use a heredoc for multi-line bodies.
Read an issue: gh issue view <number> --comments, filtering comments by jq and also fetching labels.
List issues: gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]' with appropriate --label and --state filters.
Comment on an issue: gh issue comment <number> --body "..."
Apply / remove labels: gh issue edit <number> --add-label "..." / --remove-label "..."
Close: gh issue close <number> --comment "..."

Infer the repo from git remote -v — gh does this automatically when run inside a clone.

Pull requests as a triage surface

PRs as a request surface: no. External PRs are not triaged alongside issues.

When a skill says "publish to the issue tracker"

Create a GitHub issue.

When a skill says "fetch the relevant ticket"

Run gh issue view <number> --comments.

Wayfinding operations

Used by /wayfinder. The map is a single issue with child issues as tickets.

Map: a single issue labelled wayfinder:map, holding the Notes / Decisions-so-far / Fog body. gh issue create --label wayfinder:map.
Child ticket: an issue linked to the map as a GitHub sub-issue (gh api on the sub-issues endpoint). Where sub-issues aren't enabled, add the child to a task list in the map body and put Part of #<map> at the top of the child body. Labels: wayfinder:<type> (research/prototype/grilling/task). Once claimed, the ticket is assigned to the driving dev.
Blocking: GitHub's native issue dependencies — the canonical, UI-visible representation. Add an edge with gh api --method POST repos/<owner>/<repo>/issues/<child>/dependencies/blocked_by -F issue_id=<blocker-db-id>, where <blocker-db-id> is the blocker's numeric database id (gh api repos/<owner>/<repo>/issues/<n> --jq .id, not the #number or node_id). GitHub reports issue_dependencies_summary.blocked_by (open blockers only — the live gate). Where dependencies aren't available, fall back to a Blocked by: #<n>, #<n> line at the top of the child body. A ticket is unblocked when every blocker is closed.
Frontier query: list the map's open children (gh issue list --state open, scoped to the map's sub-issues / task list), drop any with an open blocker (issue_dependencies_summary.blocked_by > 0, or an open issue in the Blocked by line) or an assignee; first in map order wins.
Claim: gh issue edit <n> --add-assignee @me — the session's first write.
Resolve: gh issue comment <n> --body "<answer>", then gh issue close <n>, then append a context pointer (gist + link) to the map's Decisions-so-far.

Read the full file on GitHub · 38 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.

5d ago First seen · 38 lines · 0 tokens per session scan A 76ab60895910

Subscribe to this mod's changes

issue-tracker is an agent published in the GitHub repository vipzhengmingming/oh-my-powers (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 788 tokens. A static security scan graded it A with 0 findings. It is 89% identical to issue-tracker, differing in 10 lines, and is treated as a copy.

Project management

issue-tracker

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

Issue tracker: GitHub

Conventions

Pull requests as a triage surface

When a skill says "publish to the issue tracker"

When a skill says "fetch the relevant ticket"

Wayfinding operations

What this file has done since we first saw it

Other agents, from other repositories

Demonstrate

analyzer

playwright-test-generator

grader

comparator

agentic-workflows