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 commands/pproenca/agent-tui/plan-tddgit 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.00013 | $0.02788 |
| Opus 5 | $0.00006 | $0.01394 |
| Sonnet 5 | $0.00003 | $0.00558 |
| Haiku 4.5 | $0.00001 | $0.00279 |
Grade A, and why
plan-tdd 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 — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Task Planning Command
Create an extensive, detailed task list using TDD methodology with carpaccio-style slicing. This command is designed for long coding sessions where comprehensive tracking is essential.
Artifact Chain
This command is part of the brainstorm → spec → plan pipeline:
.claude/specs/<feature-name>/
├── brainstorm.md ← From /brainstorm (optional)
├── spec.md ← From /spec (recommended input)
└── plan-summary.md ← Output: task plan summary
Input Priority:
- If
.claude/specs/<feature-name>/spec.mdexists → use it as primary input - If
.claude/specs/<feature-name>/brainstorm.mdexists → use it (less structured) - If neither exists → gather requirements interactively or explore codebase
Core Principles
1. Carpaccio Slicing
Every task must be:
- Atomic: Completable in a single focused action (< 30 min of work)
- Demonstrable: Has visible, verifiable output
- Valuable: Delivers a small increment of functionality
- Vertical: Touches all necessary layers (test → impl → integration)
2. TDD Workflow (Red-Green-Refactor)
For every feature, create this task chain:
- RED - Write failing test(s) first
- GREEN - Implement minimal code to pass
- REFACTOR - Clean up while keeping tests green
3. Dependency Chains
Use addBlockedBy to enforce:
- Test tasks block their implementation tasks
- Implementation tasks block refactor tasks
- Earlier phases block later phases
Execution Flow
Step 1: Load Context from Artifact Chain
Extract feature name from argument: $ARGUMENTS
Check for existing artifacts in order:
1. .claude/specs/<feature-name>/spec.md → Full specification (best)
2. .claude/specs/<feature-name>/brainstorm.md → Raw ideas (usable)
3. Neither exists → Interactive mode
If spec.md exists:
- Read the entire specification
- Extract: success criteria, scope, architecture decisions, interfaces, testing strategy
- Use these directly to inform task creation
- Skip most interactive questions (spec has answers)
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 · 363 lines · 13 tokens per session scan A 8ef72512a7f7
plan-tdd is a command published in the GitHub repository pproenca/agent-tui (113 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 2,788 once invoked, about $0.0001 per session on Opus 5. 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 commands, from other repositories
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
read
Read a specific section from an arXiv paper's HTML version (ar5iv.org).
simplify
You are an expert code simplification specialist focused on enhancing code clarity, consistency, and maintainability while preserving exact functionality. Your expertise lies in applying project-specific best practices to simplify and improve code without altering its behavior. You prioritize readable, explicit code…
index
Command "index" from thrashr888/agentkernel, covering commands, quick reference, daily drivers (root level), sandbox lifecycle (sandbox / sb) and ssh (ssh).
snapshots
Save and restore sandbox state. Snapshots capture the full filesystem of a running or stopped sandbox using docker commit.