Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/detection)<a href="https://agentmods.dev/skills/lingtai-ai/lingtai/detection"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/detection/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/detection"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/detection.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00019 | $0.00657 |
| Opus 5 | $0.00010 | $0.00329 |
| Sonnet 5 | $0.00004 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
lingtai-update-detection 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 9d 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.
What it actually says
Install-method detection
Nested lingtai-update reference. Detection is deliberately conservative.
- Read
~/.lingtai-tui/install.json(or the configured global directory) and validate thelingtai.tui.install/v1metadata. Matching the running executable, including the managedlingtai-tuialias, makes this a source/user-local install. - Otherwise, recognize Homebrew from the executable path and Homebrew
prefixes/environment, including
/opt/homebrew,/usr/local, and/home/linuxbrew/.linuxbrewpatterns. - Otherwise classify it as unknown/other. Do not run
brewmerely because it is available, and do not infer source ownership from a path alone when source metadata says otherwise.
Symlinks matter: a manually linked or development binary may not be the
Homebrew Cellar copy. Check lingtai-tui doctor output and the resolved
executable before choosing a manual command. This metadata is diagnostic and
routing information, not a credential store.
A Homebrew-detected install is not upgraded through brew: /update-tui and
lingtai-tui self-update migrate it to the native installer instead (see
reference/update-tui/SKILL.md). Migrating installs and verifies a native
binary, but does not by itself guarantee the shell will run it: on a standard
Apple-Silicon Homebrew host, /opt/homebrew/bin is earlier on PATH than
install.sh's default native bin dir, so the resolved lingtai-tui can still
be the old Homebrew one even after a "successful" install. Detection accounts
for this directly — when valid native (install.json) metadata exists but
does not match the currently resolved executable, and that executable still
resolves as Homebrew, detection reports DuplicateNativeInstall instead of
silently treating it as a plain fresh Homebrew install: the method stays
Homebrew (the resolved binary really is still Homebrew's), and every update
entry point surfaces "native installed, migration not complete, remove
Homebrew yourself" instead of re-prompting or re-running the installer. Only
once the resolved executable actually matches the native metadata does
detection report the install as source/user-local from then on — until then,
the Homebrew Cellar copy stays on disk. Removing it always requires a
concrete interactive "y" to the "Remove the old Homebrew installation now?"
prompt at startup (see reference/update-tui/SKILL.md); self-update and
doctor never uninstall it themselves, only report the manual command.
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.
- 9d ago First seen · 49 lines · 19 tokens per session scan A 9ee1b8f3686c
lingtai-update-detection is a skill published in the GitHub repository Lingtai-AI/lingtai (700 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 657 once invoked, about $0.0001 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…