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 initiationgit 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/initiation)<a href="https://agentmods.dev/skills/lingtai-ai/lingtai/initiation"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/initiation/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/initiation"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/initiation.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.00030 | $0.01240 |
| Opus 5.5 | $0.00012 | $0.00496 |
| Sonnet 5.5 | $0.00006 | $0.00248 |
| Haiku 4.5 | $0.00003 | $0.00124 |
Grade A, and why
bot-guide-initiation 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initiation: decide what is being created
Nested lingtai-bot-guide reference. Start here for a new bot; then load only the recipe, preset or channel owner needed for the chosen route.
Establish inputs and authority
- Choose a canonical
PROJECT_DIRowned by the intended user, an agent name, language (en,zh,wen), channel audience and designated maintenance owner. Check the target and parent permissions, existing.lingtai/, and running inventory. A new target is not permission to overwrite unrelated files. - Obtain explicit authorization for project creation/process launch and separately for provider/auth/config writes and external contact. Reusing a token or another agent's preset access is a privilege decision, not merely copying files.
- Preserve existing/partial state on failure. Do not retry creation over it,
delete it, call
clean/purge/nirvana, or manually fabricate.lingtai/. Recovery/deletion requires a separate human decision.
Choose the current creation surface
| Intent | Existing route and boundary |
|---|---|
| Interactive new TUI project with recipe selection | Run the installed lingtai-tui in the selected directory; follow its first-run/setup UI and lingtai-tui-help. Recipe composition remains TUI-owned. |
| New headless project bot | lingtai-tui spawn through headless bot. It creates and launches, selects plain, and emits JSON. It is not a custom-recipe selector or an installer. |
| Existing valid kernel agent without the TUI | Use installed kernel CLI help and system-manual → reference/substrate-manual/SKILL.md (§11). Verify interpreter/config ownership before running. Do not translate TUI recipe flags into imaginary kernel project flags. |
| Persistent specialist inside the existing network | Avatars, not a new project and not a channel automatically inherited from the parent. |
| Connect a channel to an existing bot | Channels; do not create a second agent merely for another entrance to the same mind. |
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 · 84 lines · 30 tokens per session scan A 4856ef8c04d2
bot-guide-initiation is a skill published in the GitHub repository Lingtai-AI/lingtai (507 stars, last pushed 6d ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,240 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…