issue-tracker

A workflow for managing a repository’s issues and product requirements documents (PRDs) through GitHub. It uses the GitHub command-line tool for these operations.

In plain words
What is it for?
Creating, viewing, updating, and managing GitHub issues and PRDs for a software repository.
Why use it?
It keeps planning and issue work in one place, reducing the need to switch between separate tracking systems or undocumented processes.

Agent

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/isak102/neowright/issue-tracker
Clone the repo
git clone --depth 1 https://github.com/isak102/neowright
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 283 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00283
Opus 5 $0.00000 $0.00142
Sonnet 5 $0.00000 $0.00057
Haiku 4.5 $0.00000 $0.00028

Measured 2d ago against content hash d290c5260303, 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 2d 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.

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

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 2d ago First seen · 23 lines · 0 tokens per session scan A d290c5260303

Subscribe to this mod's changes

issue-tracker is an agent published in the GitHub repository isak102/neowright (14 stars, last pushed 2mo ago), licensed GPL-3.0. It costs nothing until one of its globs matches a file; then it loads 283 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.

Related

Other agents, from other repositories

PullRequest Creator

An Agent to create PullRequests.

aiya000/dotfiles · 10 tokens

debugger

Performs evidence-based root-cause analysis: quotes the actual error, reproduces it, bisects what changed, forms one testable hypothesis, fixes the cause (not the symptom), and confirms the failing case now passes. Use when something is broken, a test fails, a stack trace appears, or you need fast diagnosis of a…

urmzd/dotfiles · 100 tokens

strategist

Executes write-capable multi-repo sweeps and batch operations: enumerates every target, dry-runs on one, presents a diff for approval, then applies across the full set with progress tracking and coverage verification. High blast radius (edits and runs scoped git/gh across many repos), so it gates on approval and halts…

urmzd/dotfiles · 130 tokens

writer

Authors concise, outcome-focused technical documentation for a single file: structures frontmatter and sections, leads with the action, uses tables over prose, avoids em dashes, verifies claims against source, and treats examples and gotchas as mandatory. Use for writing or rewriting one README, skill file, or API doc…

urmzd/dotfiles · 121 tokens

browser-automation-agent

Use this agent for ALL browser automation (test pages, screenshots, console errors, health checks). Never use browser tools directly. Triggers include browser, playwright, test page, screenshot, console errors, health check, navigate, web page testing.

ooloth/dotfiles · 54 tokens

nextjs-agent

Next.js development specialist using Next.js DevTools MCP. Always use this agent to query the Next.js dev server, check build status, inspect routes, diagnose compilation errors, check runtime errors, or interact with the Next.js MCP endpoint. Returns focused diagnostics and recommendations.

ooloth/dotfiles · 57 tokens