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 instructions/slima4/claude-tui/agents-mdgit clone --depth 1 https://github.com/slima4/claude-tuiWrote 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/instructions/slima4/claude-tui/agents-md)<a href="https://agentmods.dev/instructions/slima4/claude-tui/agents-md"><img src="https://agentmods.dev/badge/instructions/slima4/claude-tui/agents-md.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.00546 | $0.00546 |
| Opus 5 | $0.00273 | $0.00273 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade B, and why
claude-tui AGENTS.md scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Test tools directly without modifying `~/.claude/settings.json`: What it actually says
AGENTS.md
Quick Commands
python3 claudetui.py monitor # test monitor
python3 claudetui.py chart # test efficiency chart
python3 claudetui.py mode custom # test configurator TUI
python3 claudetui.py --help # test dispatcher
python3 claude-code-monitor/test_monitor.py -v # monitor tests
python3 claude-code-sniffer/test_sniffer.py -v # sniffer tests
PYTHONPATH=. python3 claude_tui_core/test_core.py -v # core tests
Testing
Only two tools have tests: monitor and sniffer. Run both before/after refactoring.
Gotchas (hard-won knowledge)
-
python3 claudetui.py uninstallremoves the repo directory! Use with caution - it deletes the git repo folder -
Usage API rate limiting: The OAuth usage API frequently returns 429 errors.
claude_tui_core/network.pyhandles exponential backoff (2min → 4min → 8min) and preserves cache. -
Model Data: Centralized in
claude_tui_core/models.py. Keep in sync when updating pricing. -
Status Page / Usage: Centralized logic in
claude_tui_core/network.py. -
Widget API:
widget_fn(frame, ratio) -> list[str]must return exactly 3 rows.
Local Development
Test tools directly without modifying ~/.claude/settings.json:
python3 claudetui.py monitor
python3 claudetui.py chart
To test statusline locally, edit ~/.claude/settings.json to point to your repo path instead of installed path.
Release
- Bump
_FALLBACK_VERSIONinclaudetui.py - Commit, tag (
git tag v0.X.Y), push with--tags
Key Files
- Entry point:
claudetui.py(routes subcommands to tools) - Shared UI Library:
claude_tui_components/(holdsbuild_progress_bar,build_sparkline, ANSI colors, string utils) - Shared Logic Core:
claude_tui_core/(models, network, settings/hot-reload) - Each tool in its own directory, self-contained with README
- Config:
~/.claude/claudeui.json(hot-reloads, no restart needed) - Tests:
claude_tui_core/test_core.py(unit tests for core library)
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 · 51 lines · 546 tokens per session scan B bad6fb492cc7
claude-tui AGENTS.md is an instructions file published in the GitHub repository slima4/claude-tui (41 stars, last pushed yesterday), licensed MIT. It adds 546 tokens to every session, about $0.0027 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
plan-critique-skills CLAUDE.md
Instructions for serbanghita/plan-critique-skills, covering project standards, architecture, code style, versioning and releases and documentation.
ohmyzsh-ai-cli-plugins CLAUDE.md
Instructions for gravtice/ohmyzsh-ai-cli-plugins, covering claude.md, project overview, language guidelines, core architecture and plugin structure pattern.
AIPlugHub CLAUDE.md
Instructions for ThanhWilliamLe/AIPlugHub, covering 7a-app — application source code, contributing hats, as developer, what belongs here and what does not belong here.
claude-code-optimizer CLAUDE.md
Claude Code instructions for carlosduplar/claude-code-optimizer, covering communication, principles, verification protocol, workflow and documentation.
keepup-ai-tools CLAUDE.md
Claude Code instructions for liuqi1024/keepup-ai-tools, covering keepup-ai-tools, 项目结构, 技术要点, 版本规范 and ci.
vibetags com-example-config-AsyncTestConfig.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.