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/project-boardgit 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.00793 |
| Opus 5 | $0.00000 | $0.00396 |
| Sonnet 5 | $0.00000 | $0.00159 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
project-board 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Board
GitHub Project: https://github.com/users/pproenca/projects/1
Use this Project as the progress dashboard for issues and external PRs in pproenca/agent-tui. GitHub Issues remain the source of truth for requirements and discussion; the Project is for workflow state, prioritization, and filtering.
Do not track active work in repo-local docs/exec-plans/ files. If a piece of work needs planning, create a PRD issue, split it into implementation issues, and keep this Project in sync with the labels in docs/agents/triage-labels.md.
The Project's Auto-add to project workflow is enabled for agent-tui with the filter is:issue,pr is:open, so new open issues and PRs are automatically added to the board.
Fields
- Status: GitHub's built-in project status (
Todo,In Progress,Done). - Workflow: repo-specific triage state (
Inbox,Needs Info,Ready for Agent,Ready for Human,In Progress,In Review,Blocked,Done). - Priority: urgency and ordering (
P0,P1,P2,P3). - Area: user-facing or operational area (
CLI,Daemon,PTY,RPC/API,Web UI,Docs,Release,Architecture). - Layer: Clean Architecture owner (
common,domain,usecases,adapters,infra,app,facade,web,xtask). - Size: rough implementation size (
XS,S,M,L).
Saved Views
The Project has these saved views:
- All Work: https://github.com/users/pproenca/projects/1/views/1
- Triage Inbox: https://github.com/users/pproenca/projects/1/views/2 (
workflow:Inbox) - Agent Queue: https://github.com/users/pproenca/projects/1/views/3 (
workflow:"Ready for Agent") - Human Queue: https://github.com/users/pproenca/projects/1/views/4 (
workflow:"Ready for Human") - Active Work: https://github.com/users/pproenca/projects/1/views/5 (
workflow:"In Progress") - Review: https://github.com/users/pproenca/projects/1/views/6 (
workflow:"In Review") - Architecture: https://github.com/users/pproenca/projects/1/views/7 (
area:Architecture) - Release: https://github.com/users/pproenca/projects/1/views/8 (
milestone:*)
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 · 46 lines · 0 tokens per session scan A 97ed95c7898c
project-board is an agent published in the GitHub repository pproenca/agent-tui (114 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 793 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-30.
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.
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
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.