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-updategit 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-update)<a href="https://agentmods.dev/skills/lingtai-ai/lingtai/lingtai-update"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/lingtai-update/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-update"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/lingtai-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Rogue Agent · line 32 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- high Rogue Agent · line 52 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00039 | $0.00706 |
| Opus 5 | $0.00019 | $0.00353 |
| Sonnet 5 | $0.00008 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
lingtai-update 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 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.
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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LingTai TUI update
TUI-owned operational router for the two Go deliverables this repository ships:
lingtai-tui and lingtai-portal. Read only the focused reference that matches
the problem; code, tests, ANATOMY.md, and the current installer remain the
source of truth.
This skill documents existing paths; it does not add update machinery. Python
runtime and kernel install/update/nudge behavior belongs to the kernel's
system-manual runtime/kernel update manual; use that manual for kernel work,
then return here for the TUI or portal binary boundary.
Nested reference catalog
- name: lingtai-update-install
location: reference/install/SKILL.md
description: Public installer, release assets, source fallback, and manual builds for both Go binaries.
- name: lingtai-update-command
location: reference/update-tui/SKILL.md
description: /update-tui and self-update semantics, confirmation, restart, and ownership boundaries.
- name: lingtai-update-detection
location: reference/detection/SKILL.md
description: Native install.json, source/user-local, Homebrew, symlink, and unknown-install detection.
- name: lingtai-update-diagnosis
location: reference/diagnosis/SKILL.md
description: Failure triage for updater, installer, binary, portal, and runtime symptoms.
- name: lingtai-update-homebrew
location: reference/homebrew/SKILL.md
description: Supported formula use and safe exploration of the Lingtai Homebrew tap and build logic.
- name: lingtai-update-mainland
location: reference/mainland-china/SKILL.md
description: Mainland-China routing for Go, npm, GitHub, and the lingtai.ai mirror, plus the provider-selected dependency index, without mirror guarantees.
Routing table
| Need | Read |
|---|---|
Install or build lingtai-tui and lingtai-portal |
reference/install/SKILL.md |
Understand /update-tui or lingtai-tui self-update |
reference/update-tui/SKILL.md |
| Explain why the TUI chose source, Homebrew, or unknown | reference/detection/SKILL.md |
| Diagnose a failed or partial update | reference/diagnosis/SKILL.md |
| Inspect Homebrew formula/tap behavior | reference/homebrew/SKILL.md |
| Build or fetch from mainland China, or explain which package index the installer picked | reference/mainland-china/SKILL.md |
What ships with it
6 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.
- 4d ago Changed 2693dc0cf631
- 5d ago Changed · -9 tokens per session fb13f025c700
- 12d ago First seen · 60 lines · 48 tokens per session scan A 6c2e51f48654
lingtai-update is a skill published in the GitHub repository Lingtai-AI/lingtai (673 stars, last pushed yesterday), licensed Apache-2.0. It adds 39 tokens to every session and 706 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…