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 skills/pproenca/agent-tui/tui-explorernpx skills add pproenca/agent-tui --skill tui-explorergit 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.00054 | $0.00425 |
| Opus 5 | $0.00027 | $0.00212 |
| Sonnet 5 | $0.00011 | $0.00085 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
tui-explorer 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 3d 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.
What it actually says
tui-explorer
Purpose
Generate replayable acceptance tests from discovered TUI navigation paths.
Commands
- Discover:
skills/tui-explorer/scripts/tui_explorer discover --command "<app command>"
- Verify:
skills/tui-explorer/scripts/tui_explorer verify --spec "<path-to-acceptance.md>"
Defaults
- Exploration strategy: bounded BFS.
- Safe action set:
Enter,Tab,ArrowDown,ArrowUp,ArrowRight,ArrowLeft,Esc,Space. - Risky actions are disabled unless
--allow-riskyis set. - Output directory defaults to
.agent-tui/discover/<timestamp>/. - Replay fails on scenario failure and exits non-zero.
Workflow
- Start live preview over the HTTP endpoint with
agent-tui live start --openbefore discovery so the user can watch exploration in the built-in web UI. - Run
discoverfor the target command. - Inspect generated artifacts:
acceptance.md(human-readable OpenSpec-style expectations + machine-executable steps)trace.jsonldiscover-report.json
- Run
verifyagainst the generatedacceptance.md. - Stop live preview with
agent-tui live stopafter verification.
Session handling for live preview:
- Treat browser session selection as preview-local context only.
- Do not use browser interactions to switch the daemon active session.
- On failure, inspect
verify-report.jsonand files underfailures/.
References
- Schema details:
references/schema-v1.md - Discovery mechanics:
references/discovery.md - Replay semantics:
references/replay.md
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 47 lines · 54 tokens per session scan A 03598136e2ee
tui-explorer is a skill published in the GitHub repository pproenca/agent-tui (114 stars, last pushed 5d ago), licensed MIT. It adds 54 tokens to every session and 425 once invoked, about $0.0003 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 skills, from other repositories
ptywright-testing
Build, run, record, replay, debug, and maintain deterministic terminal, TUI, PTY cassette, and browser-terminal agent regression tests with ptywright. Use when an agent needs to drive CLI/TUI apps, create ptywright scripts, configure ptywright.config., record or replay PTY output, solidify browser terminal agent flows…
agent-host-e2e-tests
Use when writing, recording, updating, or troubleshooting the agent host end-to-end tests under src/vs/platform/agentHost/test/node/e2e (black-box tests that drive the whole agent host over the AHP protocol, using a CapiReplayProxy record/replay system for Claude/Copilot/Codex). Covers adding a cross-provider test…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
docs-build
Build, preview, and validate the Uno documentation website (DocFX) locally — surface real content errors vs expected noise, drive rendered pages with Playwright, and validate external-doc commit bumps in importexternaldocs.ps1 before a PR. Use when working under doc/, editing articles/ markdown, bumping an external…
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…