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.
npx agentmods add agents/igoraguiar/bun-pg-mcp/issue-trackergit clone --depth 1 https://github.com/igoraguiar/bun-pg-mcpWrote 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.
[](https://agentmods.dev/agents/igoraguiar/bun-pg-mcp/issue-tracker)<a href="https://agentmods.dev/agents/igoraguiar/bun-pg-mcp/issue-tracker"><img src="https://agentmods.dev/badge/agents/igoraguiar/bun-pg-mcp/issue-tracker.svg" alt="Measured on agentmods" height="20"></a>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.00463 |
| Opus 5 | $0.00000 | $0.00231 |
| Sonnet 5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00046 |
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.
This is a copy
98% 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.
What it actually says
Issue tracker: Local Markdown
Issues and specs for this repo live as markdown files in .scratch/.
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 from01— never a single combined tickets file - Triage state is recorded as a
Status:line near the top of each issue file (seetriage-labels.mdfor the role strings) - Comments and conversation history append to the bottom of the file under a
## Commentsheading
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 from01, with the question in the body. AType:line records the ticket type (research/prototype/grilling/task); aStatus:line recordsclaimed/resolved. - Blocking: a
Blocked by: NN, NNline near the top. A ticket is unblocked when every file it lists isresolved. - Frontier: scan
.scratch/<effort>/issues/for files that are open, unblocked, and unclaimed; first by number wins. - Claim: set
Status: claimedand save before any work. - Resolve: append the answer under an
## Answerheading, setStatus: resolved, then append a context pointer (gist + link) to the map's Decisions-so-far inmap.md.
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.
- 4d ago First seen · 31 lines · 0 tokens per session scan A 6f38f66f9ffc
issue-tracker is an agent published in the GitHub repository igoraguiar/bun-pg-mcp (1 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 463 tokens. A static security scan graded it A with 0 findings. It is 98% identical to issue-tracker, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
product-owner
Analyzes the codebase, issues, and TODOs to propose prioritized work items. Run when deciding what to work on next or reviewing the project backlog.
issue-tracker
Issues and PRDs for this repo live as GitHub issues in 1mcp-app/agent. Use the GitHub CLI (gh) for issue operations.
triage-labels
The skills speak in terms of five canonical triage roles. This repo uses the default strings unchanged, recorded as the Status: line in each .scratch//issues/.md file.
triage-scan
You are a triage analyst. ./input.json names one repo and the exact source tree to read it against.
alg-axel
AL-Go App Provisioner Specialist — Use when asking about adding existing apps, test apps, app dependencies, or app configuration in AL-Go projects.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.