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 skills add vasilyu1983/AI-Agents-public --skill ai-coding-agents-terminal-uigit clone --depth 1 https://github.com/vasilyu1983/AI-Agents-publicWrote 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/vasilyu1983/ai-agents-public/ai-coding-agents-terminal-ui)<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/ai-coding-agents-terminal-ui"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/ai-coding-agents-terminal-ui/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/ai-coding-agents-terminal-ui"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/ai-coding-agents-terminal-ui.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 160 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.1 | $0.00045 | $0.03973 |
| Opus 5 | $0.00023 | $0.01987 |
| Sonnet 5 | $0.00009 | $0.00795 |
| Haiku 4.5 | $0.00005 | $0.00397 |
Grade A, and why
ai-coding-agents-terminal-ui 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 11d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Coding Agents Terminal UI
Use this skill to design or review the terminal-first user experience of a coding-agent runtime: REPL structure, prompt input, message rendering, command queues, virtualized history, interrupt behavior, notifications, and background-task navigation.
This skill is for terminal interaction patterns, not generic desktop app UX.
ASCII Flow
runtime events
|
v
host-owned REPL state
transcript + prompt input + command queue + background tasks + overlays
|
v
render pipeline
message model + virtualized history + notifications + task surfaces
|
v
input state machine
idle | editing | running | search | overlay | teammate view | remote/viewer
|
v
runtime action
submit, interrupt, foreground task, kill task, search, rewind, resume
Quick Reference
| Question | Read | Outcome |
|---|---|---|
| How should the REPL, prompt, and history work? | references/repl-message-input-and-history.md |
Message model, prompt queue, input behavior, interrupt handling |
| How should background work and large histories render? | references/background-work-notifications-and-virtualization.md |
Background-task UX, notifications, virtual scroll, and teammate navigation |
| What are the input states and keybindings for background navigation? | references/input-state-machine.md |
State machine, transition table, mode-specific keybindings, invariants, failure modes |
| How do ToolSearch deferred-tool results render in the REPL? | references/recipe-toolsearch-render.md |
Discovery annotation, collapse behavior, permission-prompt sequencing, scroll rules |
| What OpenAI Codex TUI patterns should be snapshot-tested? | references/openai-codex-tui-status-and-snapshot-patterns.md |
Status line/title, approval modals, hook/app-server warnings, narrow terminal states |
| What are Claude Code's real status-line fields, keybinding contexts, and Agent Teams display modes? | references/input-state-machine.md |
Verified statusLine JSON fields, keybindings.json contexts/reserved keys, in-process vs split-pane display modes |
What ships with it
9 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.
- agents/openai.yaml 346 B
- data/sources.json 7.1 KB
- learnings.consolidated.md 604 B
- learnings.md 520 B
- references/background-work-notifications-and-virtualization.md 3.0 KB
- references/input-state-machine.md 12 KB
- references/openai-codex-tui-status-and-snapshot-patterns.md 2.7 KB
- references/recipe-toolsearch-render.md 8.2 KB
- references/repl-message-input-and-history.md 2.0 KB
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.
- 11d ago First seen · 226 lines · 45 tokens per session scan A c5e3bae17dfb
ai-coding-agents-terminal-ui is a skill published in the GitHub repository vasilyu1983/AI-Agents-public (87 stars, last pushed 9d ago), licensed MIT. It adds 45 tokens to every session and 3,973 once invoked, about $0.0002 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
brand-landingpage
Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established…
wcag-audit-patterns
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.
design-inventory
Use to run the Claude Design to ClosedLoop pipeline against the current web-ui. Stage A inventories a design export zip into schema-validated findings (typed design units - screens, regions like nav bars, standalone components like a chat dialog; UX and behavioral changes; Storybook component reuse mapping; token…
mermaid-visualizer
This skill should be used when a user asks to explain a complex idea, concept, or system architecture, or when a diagram would be helpful to visualize control flows, system architectures, data flows, state machines, sequence diagrams, or entity relationships.
design-system
DESIGN.md integration for Forge — ensures visual consistency across all UI tasks through standardized design specifications.
qa-design
UI/UX design audit and verification of web best practices, including responsive/mobile-first breakpoints. Trigger when the user wants to audit the design, verify the UI/UX, check responsive behaviour, or improve the user interface.