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-customizegit 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-customize)<a href="https://agentmods.dev/skills/flanliulf/speclite/speclite-customize"><img src="https://agentmods.dev/badge/skills/flanliulf/speclite/speclite-customize.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.00066 | $0.00764 |
| Opus 5 | $0.00033 | $0.00382 |
| Sonnet 5 | $0.00013 | $0.00153 |
| Haiku 4.5 | $0.00007 | $0.00076 |
Grade A, and why
speclite-customize 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 8d 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 Customize 将用户意图转换为 {speclite-runtime-root}/custom/ 下正确放置的 TOML override。它支持探索可定制 Skill、选择 agent/workflow surface、生成稀疏 override、写入 team 或 user 文件，并验证合并结果。
[核心能力]
- 预检安装：确认 {project-root}/_speclite/ 和 runtime 脚本是否存在。
- 可定制项发现：运行 scripts/list_customizable_skills.py 扫描安装 Skill 的 customize.toml。
- surface 判断：区分 [agent]、[workflow] 或双 surface，帮助用户选择正确覆盖面。
- 稀疏 TOML 生成：只写用户要改变的字段，不复制完整 customize.toml。
- team/user 放置：将团队覆盖写入 {speclite-runtime-root}/custom/{skill-name}.toml，个人覆盖写入 {skill-name}.user.toml。
- 合并验证：优先使用 resolver，失败时按 base -> team -> user 手动解释合并结果。
[执行流程]
1. 预检 {project-root}/_speclite/；缺失时说明 Speclite 未安装并停止。
2. 运行 speclite resolve config --project-root {project-root} 获取 merged runtime config 中的 user_name 和 communication_language。
3. 分类用户意图：directed、exploratory、audit/iterate 或 cross-cutting。
4. exploratory 或 audit 场景运行 python3 {skill-root}/scripts/list_customizable_skills.py --project-root {project-root}，必要时追加 --extra-root。
5. 读取目标 Skill 的 customize.toml 和已存在覆盖文件，判断应修改 agent surface、workflow surface 或多个 workflow。
6. 生成稀疏 TOML，先展示完整内容和 diff，等待用户明确确认。
7. 写入 {speclite-runtime-root}/custom/ 下 team 或 user 覆盖文件。
8. 运行 speclite resolve customization --skill <install-path> --project-root {project-root} --key <agent-or-workflow> 验证；失败时手动合并并解释。
9. 总结写入位置、变更字段和后续迭代方式。
[注意事项]
- {speclite-runtime-root} = {project-root}/_speclite。
- 中央 config 覆盖不属于 per-skill customize，需明确说明边界。
- 如果目标 customize.toml 没暴露用户想改的字段，必须如实说明，不得发明字段。
- Override 必须稀疏，只包含用户确认的字段。
- 写文件前必须展示内容并获得明确确认。
What ships with it
4 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.
- 8d ago First seen · 40 lines · 66 tokens per session scan A 1eb95aa32f09
speclite-customize is a skill published in the GitHub repository flanliulf/SpecLite (4 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 764 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…
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…
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…
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…