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 Lingtai-AI/lingtai --skill lingtai-tui-anatomygit clone --depth 1 https://github.com/Lingtai-AI/lingtaiWrote 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/lingtai-ai/lingtai/lingtai-tui-anatomy)<a href="https://agentmods.dev/skills/lingtai-ai/lingtai/lingtai-tui-anatomy"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/lingtai-tui-anatomy/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/lingtai-ai/lingtai/lingtai-tui-anatomy"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/lingtai-tui-anatomy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00100 | $0.01376 |
| Opus 5 | $0.00050 | $0.00688 |
| Sonnet 5 | $0.00020 | $0.00275 |
| Haiku 4.5 | $0.00010 | $0.00138 |
Grade A, and why
lingtai-tui-anatomy 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 6d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LingTai Go Anatomy — navigation guide
Canonical owner
The repository-root ANATOMY.md is both the normative anatomy-of-anatomy and the
top of the distributed code-navigation graph. Per-folder ANATOMY.md files are
the content. This bundled skill is the discoverable navigation aid: when it and
the repository root disagree, the repository root governs.
An Anatomy file maps structure, connections, composition, and state beside the
code it describes. It is not a user manual, behavior contract, design history,
or test specification. The paired root CONTRACT.md owns interfaces and expected
behavior; the repository-local dev guide owns contribution workflow.
How to navigate
- Open the repository-root
ANATOMY.mdand readComponentsplusComposition. - Choose
tui/ANATOMY.mdfor terminal UI, subprocess launch, agent inventory, lifecycle controls, and/viz; chooseportal/ANATOMY.mdfor the web server, embedded frontend, topology, and replay. - Descend to the named package Anatomy and open the cited
file:linerange. - Treat code as structural truth. If a citation or ownership claim drifted, update the relevant Anatomy in the same change.
- Use search for enumeration only (every callsite/file); use Anatomy for structural ownership and data-flow questions.
Runtime-boundary route
For questions such as “Does closing the TUI stop my agent?”, “How do I attach again?”, “Who owns lifecycle?”, or “Should I add launchd?”:
- Start at root
ANATOMY.md→tui/ANATOMY.md, sectionRuntime/control-surface boundary. - Follow its same-repo anchors for normal Bubble Tea quit, kernel subprocess
launch and duplicate-process prevention, startup attachment, explicit
/sleep//suspend//cpr//refresh, inventory, and Portal process release. - Use
portal/ANATOMY.mdfor Portal's own process and shutdown boundary. - Load
lingtai-kernel-anatomyfor exact kernel heartbeat, listener, signal, and lifecycle internals. Do not cite sibling-repo files from TUI Anatomy.
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.
- 6d ago Changed · -1 lines · -12 tokens per session 97315b2d8882
- 13d ago First seen · 111 lines · 112 tokens per session scan A a90e87059ac3
lingtai-tui-anatomy is a skill published in the GitHub repository Lingtai-AI/lingtai (677 stars, last pushed yesterday), licensed Apache-2.0. It adds 100 tokens to every session and 1,376 once invoked, about $0.0005 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
write-zot-themes
Help the user create, install, or package zot themes, including theme-only extensions.
pvetui-cli
Use when querying or managing a Proxmox VE cluster via the pvetui CLI — listing nodes, guests, and tasks; creating and migrating VMs and LXC containers; managing storage content, downloading templates and OCI images, restoring backups, and installing Proxmox Community Scripts when the plugin is enabled. Requires…
code-review
Run a thorough self-review pass on the most recent change.
test-fix
Diagnose and minimally fix a failing test, then re-run.
secret-review
Check a change for accidentally exposed credentials and private data.
writing-git-commits
Write clear, focused Git commit messages and keep commits easy to review.