agentmods.dev

issue-tracker

Instructions for using GitHub as the issue tracker, where a project records bugs, tasks, and specifications.

In plain words
What is it for?
Use them to manage GitHub issues and, when the repository allows it, handle pull requests as part of issue triage.
Why use it?
They give the coding assistant one consistent way to find, create, update, label, comment on, and close issues.

Agent

42k 3d ago A scan 0 tokens original MIT
View the source file amruthpillai/reactive-resume
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/amruthpillai/reactive-resume/issue-tracker
Clone the repo
git clone --depth 1 https://github.com/amruthpillai/reactive-resume
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 804 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 $0.00000 $0.00804
Opus 5 $0.00000 $0.00402
Sonnet 5 $0.00000 $0.00161
Haiku 4.5 $0.00000 $0.00080

Measured yesterday against content hash 7e1c98c25abd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

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

How it starts

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

Issue tracker: GitHub

Issues and specs 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. (Set to yes if this repo treats external PRs as feature requests; /triage reads this flag.)

When set to yes, PRs run through the same labels and states as issues, using the gh pr equivalents:

  • Read a PR: gh pr view <number> --comments and gh pr diff <number> for the diff.
  • List external PRs for triage: gh pr list --state open --json number,title,body,labels,author,authorAssociation,comments then keep only authorAssociation of CONTRIBUTOR, FIRST_TIME_CONTRIBUTOR, or NONE.
  • Comment / label / close: gh pr comment, gh pr edit --add-label/--remove-label, gh pr close.

GitHub shares one number space across issues and PRs. Resolve bare #42 with gh pr view 42, then fall back to gh issue view 42.

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. Map is one issue with child issues as tickets.

  • Map: issue labelled wayfinder:map, holding Notes / Decisions-so-far / Fog. Create with gh issue create --label wayfinder:map.
  • Child ticket: issue linked as a GitHub sub-issue. Where sub-issues are unavailable, add it to a task list in map body and put Part of #<map> atop child body. Labels: wayfinder:<type> (research, prototype, grilling, or task). Assign ticket to driving developer once claimed.
  • Blocking: use GitHub native issue dependencies. Add with gh api --method POST repos/<owner>/<repo>/issues/<child>/dependencies/blocked_by -F issue_id=<blocker-db-id>, where database ID comes from gh api repos/<owner>/<repo>/issues/<n> --jq .id. Where unavailable, use Blocked by: #<n>, #<n> atop child body.
  • Frontier query: list map’s open children, drop assigned tickets and tickets with open blockers, then select first in map order.
  • Claim: gh issue edit <n> --add-assignee @me.
  • Resolve: comment with answer, close child, then append context pointer to map’s Decisions-so-far.

Read the full file on GitHub · 46 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. yesterday First seen · 46 lines · 0 tokens per session scan A 7e1c98c25abd

Subscribe to this mod's changes

issue-tracker is an agent published in the GitHub repository amruthpillai/reactive-resume (41,957 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 804 tokens. 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.

DebuggingFrontendProject managementReActaidsh-pluginhacktoberfestresume-builderself-hosted
Related

Other agents, from other repositories

triage-labels

The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.

yuqie6/ProductFlow · 0 tokens

triage-issues-and-prs

GitHub issue and PR triage agent for slopus/happy. Use when you need to: review open issues/PRs, find duplicates, identify what needs a reply, close resolved items, draft maintainer responses, or get a status overview of the backlog. Invoke with /triage or when asked about issues, PRs, contributors, or community…

slopus/happy · 82 tokens

trellis-check

Code quality check expert. Reviews code changes against specs and self-fixes issues.

yuqie6/ProductFlow · 20 tokens

trellis-research

Code and tech search expert. Finds files, patterns, and tech solutions, and PERSISTS every finding to the current task's research/ directory. No code modifications outside that directory.

yuqie6/ProductFlow · 42 tokens

trellis-implement

Code implementation expert. Understands specs and requirements, then implements features. No git commit allowed.

yuqie6/ProductFlow · 24 tokens

check

Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.

yuqie6/ProductFlow · 34 tokens