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 channelsgit 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/channels)<a href="https://agentmods.dev/skills/lingtai-ai/lingtai/channels"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/channels/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/channels"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/channels.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.00026 | $0.00849 |
| Opus 5.5 | $0.00010 | $0.00340 |
| Sonnet 5.5 | $0.00005 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
bot-guide-channels 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Channels: one mind, explicit bridges
Nested lingtai-bot-guide reference. Multiple channels can reach the same agent;
a new channel is not automatically a new bot/process or a privileged command
interface. /refresh sent as chat text does not bypass authorization.
Load the exact owner before editing
Discover mcp-manual → reference/curated-addons.md in the installed skills
catalog. It owns the four-step curated setup, registry/module mapping, active
activation spec, agent-relative config paths, credentials, and acceptance checks.
Read the selected upstream README when provider details are needed:
| Supported curated bridge | Exact upstream documentation route |
|---|---|
| Telegram | lingtai-telegram README |
| Feishu / Lark | lingtai-feishu README |
| lingtai-wechat README; curated owner also holds bootstrap/session-expiry checklist | |
| lingtai-whatsapp README | |
| IMAP / SMTP email | lingtai-imap README |
| Cloud Mail | cloud-mail README; LingTai client fields/action limits belong to curated-addons.md and the mounted cloud_mail manual |
These homepage names are provenance/docs, not a recommendation to install
old standalone wheels. Current curated servers ship in the kernel distribution
as lingtai.mcp_servers.*. Check the installed owner's catalog if support or
module mapping differs; upstream main docs alone are not installed-version proof.
No channel secret/auth schemas are copied into this reference.
For another service, discover mcp-manual →
reference/third-party-and-legacy.md and that server's README/homepage. Do not
claim an unlisted channel is curated or that the Telegram helper implements it.
For protocol/LICC questions use lingtai-kernel-anatomy →
reference/mcp-protocol.md, not a parallel setup recipe.
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 · 61 lines · 26 tokens per session scan A 8c9b1185ca8e
bot-guide-channels is a skill published in the GitHub repository Lingtai-AI/lingtai (507 stars, last pushed 6d ago), licensed Apache-2.0. It adds 26 tokens to every session and 849 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…