issue-tracker

A repository issue tracker built around GitHub Issues, the discussion and task records attached to a GitHub code project. It uses the `gh` command-line tool for all issue and pull-request work.

In plain words
What is it for?
Creating, reading, updating, and managing GitHub Issues and pull requests for the repository.
Why use it?
It keeps project requirements and tasks in one shared place, avoiding separate tracking documents. Using one command-line route also makes issue and pull-request work consistent.

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/cuevaio/normal/issue-tracker
Clone the repo
git clone --depth 1 https://github.com/cuevaio/normal
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 996 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.00996
Opus 5 $0.00000 $0.00498
Sonnet 5 $0.00000 $0.00199
Haiku 4.5 $0.00000 $0.00100

Measured yesterday against content hash 0a6ce1167aef, 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

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-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. yesterday First seen · 46 lines · 0 tokens per session scan A 0a6ce1167aef

Subscribe to this mod's changes

issue-tracker is an agent published in the GitHub repository cuevaio/normal (11 stars, last pushed 5d ago), licensed AGPL-3.0. It costs nothing until one of its globs matches a file; then it loads 996 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-31.