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/lyhcode/agent-skills/textual-tuinpx skills add lyhcode/agent-skills --skill textual-tuigit clone --depth 1 https://github.com/lyhcode/agent-skillsWrote 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/skills/lyhcode/agent-skills/textual-tui)<a href="https://agentmods.dev/skills/lyhcode/agent-skills/textual-tui"><img src="https://agentmods.dev/badge/skills/lyhcode/agent-skills/textual-tui.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.00132 | $0.02997 |
| Opus 5 | $0.00066 | $0.01499 |
| Sonnet 5 | $0.00026 | $0.00599 |
| Haiku 4.5 | $0.00013 | $0.00300 |
Grade A, and why
textual-tui scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = await asyncio.to_thread(requests.get, url) How it starts
The opening of the file, as written. The whole thing — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Textual TUI Development
Build rich terminal user interfaces in Python using the Textual framework (v8.x).
Quick Start
pip install textual
Minimal app:
from textual.app import App, ComposeResult
from textual.widgets import Header, Footer, Static
class MyApp(App):
TITLE = "My App"
CSS_PATH = "app.tcss" # or use CSS = "..." inline
BINDINGS = [
("q", "quit", "Quit"),
]
def compose(self) -> ComposeResult:
yield Header()
yield Static("Hello, World!")
yield Footer()
if __name__ == "__main__":
MyApp().run()
Run in dev mode for live CSS editing:
textual run --dev app.py
Core Architecture
App Lifecycle
compose()— Yield widgets to build the initial UI (called once per screen)on_mount()— Post-composition setup (fetch data, configure state)run()— Enters terminal mode, starts event loopexit(return_value)— Leaves terminal mode
Widget Composition
Widgets are composed declaratively by yielding them from compose(). Use containers for layout:
from textual.containers import Horizontal, Vertical, Grid
from textual.widgets import Button, Input, Static
def compose(self) -> ComposeResult:
yield Header()
with Horizontal():
with Vertical(id="sidebar"):
yield Button("New", id="new")
yield Button("Open", id="open")
with Vertical(id="main"):
yield Input(placeholder="Search...")
yield Static("Content area")
yield Footer()
The with context manager syntax nests widgets inside containers.
Dynamic Widget Mounting
Add or remove widgets at runtime:
async def on_button_pressed(self, event: Button.Pressed) -> None:
await self.mount(Static("New widget"), after=self.query_one("#main"))
self.query_one("#old").remove()
Layout
Three layout modes, set on the parent container:
Vertical (Default)
Children stack top-to-bottom. They expand to fill width automatically.
What ships with it
3 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 · 464 lines · 132 tokens per session scan A 3aa663a341f6
textual-tui is a skill published in the GitHub repository lyhcode/agent-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 132 tokens to every session and 2,997 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…