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/pproenca/agent-tui/issue-trackergit clone --depth 1 https://github.com/pproenca/agent-tuiWhat 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.01213 |
| Opus 5 | $0.00000 | $0.00607 |
| Sonnet 5 | $0.00000 | $0.00243 |
| Haiku 4.5 | $0.00000 | $0.00121 |
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.
This is a copy
88% identical to issue-tracker — 30 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker: GitHub
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
Progress is tracked in the agent-tui Roadmap GitHub Project:
- Project URL: https://github.com/users/pproenca/projects/1
- Project owner:
pproenca - Project number:
1
See docs/agents/project-board.md for field meanings and label-to-workflow conventions.
Workflow source of truth
This repo uses the Matt Pocock skills workflow instead of repo-local exec plans.
- Do not create or update
docs/exec-plans/files for new work. - PRDs belong in GitHub Issues.
- Implementation work should be split into independently grabbable GitHub issues, usually via
to-prdandto-issues. - Use labels plus the
agent-tui RoadmapProject fields to represent workflow state. - When migrating an existing exec plan, publish the PRD and slice issues to GitHub, link the issue set, then remove the local plan artifact.
Conventions
- Create an issue:
gh issue create --title "..." --body "...". Use a heredoc for multi-line bodies. - Read an issue:
gh issue view <number> --comments, filtering comments byjqand also fetching labels. - List issues:
gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]'with appropriate--labeland--statefilters. - Comment on an issue:
gh issue comment <number> --body "..." - Apply / remove labels:
gh issue edit <number> --add-label "..."/--remove-label "..." - Close:
gh issue close <number> --comment "..."
Infer the repo from git remote -v -- gh does this automatically when run inside a clone.
Pull requests as a triage surface
PRs as a request surface: yes.
External PRs from non-collaborators should be triaged through the same label/state workflow as issues. Collaborator PRs stay out of that queue.
When set to yes, PRs run through the same labels and states as issues, using the gh pr equivalents:
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.
- 2d ago First seen · 66 lines · 0 tokens per session scan A 81bc8feaa365
issue-tracker is an agent published in the GitHub repository pproenca/agent-tui (113 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,213 tokens. A static security scan graded it A with 0 findings. It is 88% identical to issue-tracker, differing in 30 lines, and is treated as a copy.
Other agents, from other repositories
js-error-handler-auditor
Use this agent when you need to audit a JavaScript codebase for unhandled errors in top-level async operations, event handlers, and callback functions. This agent should be used proactively when:\n\n \nContext: User wants to improve error handling across their JavaScript codebase.\nuser: "Can you check if we're…
tauri-axum-parity-checker
Detects drift between the Tauri desktop command surface and the Axum WebUI server surface. Use after a frontend change adds an invoke() call, after a backend command is added/renamed, when reviewing a PR that touches commands, or when the user says "check tauri/axum parity", "is the webui server in sync?". A command…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
html-reader
Background agent for reading ar5iv.org HTML papers using agent-browser CLI.
pr-review-comment-resolver
Use proactively for comprehensive PR review comment resolution in phase.rs. Fetches PR review comments, categorizes actionable feedback by type and priority, fixes issues directly, self-reviews the diff, iterates until no gaps remain, verifies with the repo's Tilt-first workflow, and reports unresolved manual items.
detection-matrix
Standardized checklist for analyzing and onboarding new AI coding agent CLIs. Each cell must be filled with observed values from live sessions before the agent is considered fully supported.