What is issue-tracker?

A local issue tracker that stores project specifications and implementation tickets as Markdown files in the .scratch/ folder. Markdown is a plain-text format commonly used for readable project documents.

Use it to create feature specifications, add one issue file per implementation ticket, record triage status, and append discussion history.

It keeps issue details, status, and comments organized in files that remain local and are ignored by Git.

issue-tracker — Agent by Xsxdot

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/xsxdot/super-dev/issue-tracker

Clone the repo

git clone --depth 1 https://github.com/Xsxdot/super-dev

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 489 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 92% 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	$0.00000	$0.00489
Opus 5	$0.00000	$0.00244
Sonnet 5	$0.00000	$0.00098
Haiku 4.5	$0.00000	$0.00049

Measured yesterday against content hash 93543f21f31e, 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.

Origin

This is a copy

92% identical to issue-tracker — 2 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 · 31 lines

What it actually says

Issue tracker: Local Markdown

Issues and specs (you may know a spec as a PRD) for this repo live as markdown files in .scratch/. The entire .scratch/ directory is local-only and ignored by Git.

Conventions

One feature per directory: .scratch/<feature-slug>/
The spec is .scratch/<feature-slug>/spec.md
Implementation issues are one file per ticket at .scratch/<feature-slug>/issues/<NN>-<slug>.md, numbered from 01 — never a single combined tickets file
Triage state is recorded as a Status: line near the top of each issue file (see triage-labels.md for the role strings)
Comments and conversation history append to the bottom of the file under a ## Comments heading

When a skill says "publish to the issue tracker"

Create a new file under .scratch/<feature-slug>/ (creating the directory if needed).

When a skill says "fetch the relevant ticket"

Read the file at the referenced path. The user will normally pass the path or the issue number directly.

Wayfinding operations

Used by /wayfinder. The map is a file with one child file per ticket.

Map: .scratch/<effort>/map.md — the Notes / Decisions-so-far / Fog body.
Child ticket: .scratch/<effort>/issues/NN-<slug>.md, numbered from 01, with the question in the body. A Type: line records the ticket type (research/prototype/grilling/task); a Status: line records claimed/resolved.
Blocking: a Blocked by: NN, NN line near the top. A ticket is unblocked when every file it lists is resolved.
Frontier: scan .scratch/<effort>/issues/ for files that are open, unblocked, and unclaimed; first by number wins.
Claim: set Status: claimed and save before any work.
Resolve: append the answer under an ## Answer heading, set Status: resolved, then append a context pointer (gist + link) to the map's Decisions-so-far in map.md.

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.

yesterday First seen · 31 lines · 0 tokens per session scan A 93543f21f31e

Subscribe to this mod's changes

issue-tracker is an agent published in the GitHub repository Xsxdot/super-dev (1 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 489 tokens. A static security scan graded it A with 0 findings. It is 92% identical to issue-tracker, differing in 2 lines, and is treated as a copy.

Git and workflow Project management Writing and docs ai ai-tools claude-code codex cursor developer-tools

issue-tracker