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 operationsgit 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/operations)<a href="https://agentmods.dev/skills/lingtai-ai/lingtai/operations"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/operations/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/operations"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/operations.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.00027 | $0.01219 |
| Opus 5.5 | $0.00011 | $0.00488 |
| Sonnet 5.5 | $0.00005 | $0.00244 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
bot-guide-operations 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 10d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification, maintenance and recovery
Nested lingtai-bot-guide reference. This owns the bot acceptance sequence; focused manuals retain exact tool/lifecycle/auth semantics.
Acceptance: prove the whole path
- Inventory the target:
lingtai-tui list "$PROJECT_DIR"and the published manifest/heartbeat. Confirm one intended agent, not a duplicate, correct project/owner/admin role and approved active/default/allowed presets. - Inspect bridge registration and live tool surface separately. Discover
mcp-manual→reference/curated-addons.md(or third-party owner). A registered row, cached account identity, helperconfigured, PID or heartbeat is not proof that the listener/account is mounted or processing inbound events. - Ask the human/approved producer to send a fresh harmless message from an
allowed account. Observe receipt at the host and issue one authorized reply
on the same channel using the mounted channel's current manual/schema.
Provider
getMeor an outbound send alone is insufficient. Do not run a second Telegram long poller or send unrequested probes to users/peers. - Validate audience restriction with a human-approved test identity where available. If that test is unavailable, mark access-denial proof pending; do not claim it passed or open the allowlist to work around it.
- Send a sanitized human receipt: creation vs configuration vs end-to-end status, intended bot/account (non-secret public identity only), test outcome, gaps, maintenance owner and recovery route. Never attach raw logs/config/credentials or private directory/user IDs. A tool result alone is not the human handoff.
Maintenance: route by symptom
| Need | Discover owner, then lower node |
|---|---|
| Ordinary reload or model/preset swap | system-manual → reference/refresh-precheck/SKILL.md; preset operation activation-session-refresh in lingtai-preset-skill |
| Sleep/suspend/CPR or duplicate/quiet process | system-manual → reference/substrate-manual/SKILL.md; live system schema owns exact action authority |
| TUI binary/install provenance or upgrade | lingtai-update → reference/detection/SKILL.md, reference/update-tui/SKILL.md or reference/diagnosis/SKILL.md |
| Kernel version/nudge, source/venv cutover | system-manual → reference/runtime-update-checks/SKILL.md; update is installer-owned, refresh does not install code |
| Saved preset/provider login/model error | lingtai-preset-skill provider child plus reference/operations/troubleshooting-migration/SKILL.md; swiss-knife → reference/preset-health/SKILL.md for read-only diagnosis |
| Registered MCP missing tools or moved venv | mcp-manual → reference/troubleshooting.md and reference/curated-addons.md (child-runtime/venv-swap sections) |
| Source/runtime mismatch after cutover | lingtai-dev-guide → reference/runtime-self-check/SKILL.md, only for cutover/mismatch, not every normal reload |
| Durable behavior/identity, memory or restart handoff | context-manual, psyche-manual, knowledge-manual; selected owner, not copied memory |
| Scheduled service or shell background job | shell-manual root async-supervision rules or the scheduled-work reference selected by its router |
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.
- 10d ago First seen · 77 lines · 27 tokens per session scan A b225a1d2b72e
bot-guide-operations is a skill published in the GitHub repository Lingtai-AI/lingtai (507 stars, last pushed 6d ago), licensed Apache-2.0. It adds 27 tokens to every session and 1,219 once invoked, about $0.0001 per session on Opus 5.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-10-14.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…