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 runtime-self-checkgit 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/runtime-self-check)<a href="https://agentmods.dev/skills/lingtai-ai/lingtai/runtime-self-check"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/runtime-self-check/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/runtime-self-check"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/runtime-self-check.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.00122 | $0.04432 |
| Opus 5 | $0.00061 | $0.02216 |
| Sonnet 5 | $0.00024 | $0.00886 |
| Haiku 4.5 | $0.00012 | $0.00443 |
Grade A, and why
dev-guide-runtime-self-check 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.
How it starts
The opening of the file, as written. The whole thing — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Runtime Self-Check
Nested lingtai-dev-guide reference. Read this after the top-level router sends you here whenever you need to verify what code is actually running and report it without leaking secrets. It consolidates the most frequently re-implemented diagnostic in the network: the post-refresh "which runtime am I executing?" probe.
Core principle
A read-only diagnostic — probe, confirm, report. The only writes allowed are
developer rebuilds you were asked to do (make build, editable reinstall). Never
paste secrets into a report: redact tokens, keys, chat IDs, and private absolute
paths, preferring <your-lingtai-checkout> / ~/.lingtai-tui/... forms.
When to use
- Right after a
refresh, a branch/worktree switch, an editable reinstall, a preset swap, or any MCP/addon config change. - A fix is merged/built but old behaviour persists ("did it actually load?").
- A fix is imported yet a long-lived service/adapter/cache still serves stale behaviour — source-on-disk ≠ rebuilt-at-runtime (see §6).
- An MCP boot failure needs source-of-truth checks, or a maintainer needs a safe evidence pack.
Patch-to-self checklist — merged PR ≠ live runtime
To test a kernel/TUI fix on the agent you are currently speaking through, do all of these. Skipping step 1 is how agents repeatedly refresh stale code and conclude the fix failed.
- Find the runtime import path. Run the §1 probe — runtime venv Python, not
pythonon PATH. - Compare HEADs. If the agent imports
/B/lingtai-kernelbut your PR merged in/A/lingtai-kernel, update/B(git fetch origin main && git pull --ff-only origin main) or reinstall the intended checkout into the runtime venv. Do not edit protected dirty checkouts; stop and report if the fast-forward is not clean. - Refresh only after the imported source/package is right.
refreshreloads from the configured runtime environment; it does not fetch or fast-forward a source tree for you. - Do an in-situ probe. Verify live behaviour or metadata changed on this
agent — a tool result
_meta, a token-ledger field, another direct observable. Source greps and import probes are necessary but not sufficient. - Report evidence. Runtime Python, import path, old/new HEAD, action taken (fast-forward / editable reinstall / rebuild), refresh result, live probe.
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 · 362 lines · 122 tokens per session scan A 1b5248fb7c42
dev-guide-runtime-self-check is a skill published in the GitHub repository Lingtai-AI/lingtai (700 stars, last pushed today), licensed Apache-2.0. It adds 122 tokens to every session and 4,432 once invoked, about $0.0006 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.