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 flanliulf/SpecLite --skill speclite-helpgit clone --depth 1 https://github.com/flanliulf/SpecLiteWrote 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/flanliulf/speclite/speclite-help)<a href="https://agentmods.dev/skills/flanliulf/speclite/speclite-help"><img src="https://agentmods.dev/badge/skills/flanliulf/speclite/speclite-help.svg" alt="Measured on agentmods" 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.00068 | $0.00640 |
| Opus 5 | $0.00034 | $0.00320 |
| Sonnet 5 | $0.00014 | $0.00128 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
speclite-help 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 6d 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
[技能说明] Speclite Help 用于帮助用户理解当前工作流位置、已完成内容、下一步建议和可调用 Skill。它从 Speclite runtime catalog、配置、产物、项目知识和模块文档中取证，不凭空猜测项目状态。
[核心能力] - 状态定位：判断用户所处模块和阶段，并识别可能已完成的产物。 - 下一步推荐：按 phase、preceded-by、followed-by、required 和 outputs 推荐下一批 Skill。 - 调用说明：给出 Skill name、menu code、action context 和可用 args。 - 快速启动建议：当只有一个明确下一步时，主动询问是否立即运行。 - 通用问答：对不映射到具体 Skill 的问题，读取模块文档和项目知识后回答。 - 不过载输出：只展示与当前上下文相关的项目和步骤。
[执行流程]
1. 读取 {speclite-runtime-root}/_config/help-index.json；如不存在，尝试读取 {project-root}/_speclite/_config/help-index.json。如需阶段或产物路由证据，读取同目录的 phase-coverage.json。
2. 运行 speclite resolve config --project-root {project-root} 解析 merged runtime config 中的 output-location、communication_language 和 project_knowledge。
3. 按 catalog 的 outputs pattern 搜索已完成产物；必要时读取内容作为推荐依据。
4. 如果 project_knowledge 指向存在路径，读取相关文件作为项目上下文。
5. 对相关 docs/、Skill references/ 或项目知识文件，按需读取，用于回答一般问题。
6. 根据 phase、sequencing 和 required gate 输出推荐项；可选项在前，下一个 required 项明确标注。
7. 若用户问题已有明确目标，只回答该目标并给出如何调用。
[注意事项]
- {speclite-runtime-root} = {project-root}/_speclite。
- 所有输出使用 {communication_language}。
- 推荐每个 Skill 在 fresh context window 中运行。
- 不得制造项目特定事实；缺少证据时说明无法确认。
- 当前运行规约不得依赖 BMAD catalog 或 YAML 配置。
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 37 lines · 68 tokens per session scan A 9b4d23a35586
speclite-help is a skill published in the GitHub repository flanliulf/SpecLite (4 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 640 once invoked, about $0.0003 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-31.
Other skills, from other repositories
lain
Structural code intelligence for AI coding agents. Use this skill when the user wants to understand how a codebase is organized (modules, call graphs, file dependencies), find where to start reading, trace the impact of a change, find code by meaning, or understand what a symbol does in its full context. Do NOT use…
botpipe-workflow-authoring
Author, review, and improve Botpipe workflows. Use when Codex is asked to create packaged or workspace-local Botpipe workflows, convert codebases into workflows, design provider-heavy producer/verifier steps, write Botpipe prompts/contracts, inspect Botpipe traces, or apply Codex CLI/gpt-5.5 workflow patterns.
intake
The planning front-door. Captures feature ideas and bugs as graded rows in the root INTAKE.md ledger. Use it when the user says "log an idea", "capture a bug", "add to the backlog", "note this down", "track this feature", or invokes /intake. Owns the requirements interview — fleshes out thin ideas, proactively…
merge
The ship gate — the only skill that merges. --staging merges the feature→staging PR on green CI, deploys, verifies, emits a human test script and stamps the staging sign-off on approval. --production ships the double-confirmed release to main and deploys production. Never self-certifies staging; nothing reaches main…
pre-merge
The CI gate. Takes a feature branch from "eng says done" to "PR open against staging with green checks". Runs the project's preflight-resolved pipeline from devkit/policy.json components[]: sync → parallel correctness + security waves → coverage → regression tail → security/migration → PRD-consistency → open PR. Emits…
msg
Root menu for msg skills, plus harness modes. --init is the one-time project bootstrap — use it when the user says "initialise project", "bootstrap repo", "set up the framework", "start a new project", or asks to set up project structure in an empty repo. Other modes: --init-staging (add a staging branch), --update…