issue-tracker

issue-tracker is an agent for coding agents from b34nst4lk/vestibule. It costs 0 tokens per session (286 once invoked), scanned A, original, MIT.

A repository guide for tracking work as GitHub issues, the tickets used to report and discuss software tasks. It defines labels, parent links, dependencies, and records of closed decisions.

In plain words
What is it for?
Use it to create, label, link, resolve, and document GitHub issues for maps, security, user experience, publishing, code quality, and research.
Why use it?
It gives agents and developers one consistent way to organize open work and explain how tickets relate to each other.

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/b34nst4lk/vestibule/issue-tracker
Clone the repo
git clone --depth 1 https://github.com/b34nst4lk/vestibule

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.

agentmods badge for issue-tracker

README.md
[![agentmods](https://agentmods.dev/badge/agents/b34nst4lk/vestibule/issue-tracker.svg)](https://agentmods.dev/agents/b34nst4lk/vestibule/issue-tracker)
Your own site
<a href="https://agentmods.dev/agents/b34nst4lk/vestibule/issue-tracker"><img src="https://agentmods.dev/badge/agents/b34nst4lk/vestibule/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 286 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.00286
Opus 5 $0.00000 $0.00143
Sonnet 5 $0.00000 $0.00057
Haiku 4.5 $0.00000 $0.00029

Measured 4d ago against content hash 80ab33deade2, 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 4d 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 · 35 lines

What it actually says

Issue Tracker — GitHub Issues

This repo tracks open issues as GitHub issues on b34nst4lk/vestibule.

Open tickets

Open tickets (including wayfinder maps and their child tickets) live as GitHub issues. They use the wayfinder:* labels (wayfinder:map, wayfinder:security, wayfinder:ux, wayfinder:publishing, wayfinder:code-quality, wayfinder:research).

Parent/child relationships

GitHub sub-issues are not enabled for this repo, so the parent relationship uses a body convention: each child ticket's body begins with a > **Parent:** line linking to its map issue.

Blocking/dependencies

GitHub sub-issues (native blocking) are not available. Use the body convention: reference the blocking issue by link in the ticket body.

Closed decision records

Closed tickets are retained as markdown files under .scratch/ as a local record of decisions made. They are not duplicated on GitHub.

Resolving an issue

To close a GitHub issue:

  1. Post the resolution as a comment on the issue.
  2. Close the issue.
  3. Append a context pointer to the map's Decisions so far section.
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. 4d ago First seen · 35 lines · 0 tokens per session scan A 80ab33deade2

Subscribe to this mod's changes

issue-tracker is an agent published in the GitHub repository b34nst4lk/vestibule (0 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 286 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.