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-skill-lintgit 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-skill-lint)<a href="https://agentmods.dev/skills/flanliulf/speclite/speclite-skill-lint"><img src="https://agentmods.dev/badge/skills/flanliulf/speclite/speclite-skill-lint/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/flanliulf/speclite/speclite-skill-lint"><img src="https://agentmods.dev/badge/skills/flanliulf/speclite/speclite-skill-lint.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.00080 | $0.01148 |
| Opus 5 | $0.00040 | $0.00574 |
| Sonnet 5 | $0.00016 | $0.00230 |
| Haiku 4.5 | $0.00008 | $0.00115 |
Grade A, and why
speclite-skill-lint 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.
What it actually says
[Overview（技能说明）]
纯只读的 Skill 规范检查器，对指定 Skill 目录执行 36 条合规规则扫描，生成结构化检查报告。不修改任何文件，仅报告问题并提供修复建议。完整规则见 references/check-rules.md，详细扫描流程见 references/lint-workflow.md。
[Core Capabilities（核心能力）]
- YAML 头部验证：检查 name、description、allowed-tools、metadata 字段契约和安全边界是否符合开放标准。
- description 质量分析：验证三段式结构、中英文双语触发词覆盖、触发词具体性和尖括号安全。
- 文件结构合规：检查 SKILL.md、SKILL.en.md、CHANGELOG.md、目录命名、README.md 禁止项、保留前缀和 speclite- 命名空间前缀。
- 版本与 mirror 一致性：验证 SKILL.md、SKILL.en.md、CHANGELOG.md 的版本、YAML 和引用路径同步。
- 正文与 Workflow density 检查：统计正文长度、Workflow 长度和占比，识别需要抽到 references/ 的过重流程，并检查 fixed path hard gate 是否有 owning SPEC 或 equivalent implementation policy。
- 配置引用分类检查：识别本地定义、本地占位引用、runtime config、artifact path、workflow 变量、模板占位符、schema 字段和外部项目引用，避免把可解释引用误报为配置缺失。
- 命名与文件分类检查：检查 references/、scripts/、assets/ 的命名和职责边界。
- 结构化报告输出：按 Error 与 Warning 输出规则表、摘要和具体修复建议。
[Workflow（执行流程）]
本 Skill 采用扫描→报告→修复建议→重新扫描的迭代模式。完整步骤见 references/lint-workflow.md；入口仅保留阶段路由，执行细则以 reference 为准。
Step 1：定位目标 Skill
接收完整目录、Skill 名称或"所有 Skill"。按 `assets/source/speclite/`、`.claude/skills/`、`.agents/skills/`、`.codex/skills/` 的实际存在目录搜索，目标必须包含 SKILL.md。
Step 2：读取规则与统计密度
读取 `references/check-rules.md` 和 `references/lint-workflow.md`。对目标目录运行只读脚本：
`python3 scripts/check_skill_density.py <skill-dir>`
使用脚本 JSON 结果作为 BODY-07 与 BODY-08 的唯一判断来源。
Step 3：执行 36 条规则扫描
按 `references/lint-workflow.md` 的分组流程检查 YAML、description、文件结构、版本、正文、命名、mirror、分类、`speclite-` 前缀和 Workflow density。不得修改目标文件。
Step 4：输出报告并支持复查
输出标准表格：规则 ID、检查项、状态、详情、修复建议。用户修复后说"重新检查"、"re-lint"或"再查一次"时，重新执行 Step 2-4 并标注已修复和新增问题。
[Notes（注意事项）]
- 本 Skill 只读，绝不修改文件；Bash 仅可用于运行 scripts/check_skill_density.py 这类只读统计脚本。
- Error 表示硬性合规问题；Warning 表示质量、可维护性或渐进式披露风险。
- BODY-07 阈值固定为 workflow_chars > 1500 且 workflow_ratio > 0.5；BODY-08 在命中 BODY-07 且无 workflow reference 时提示抽取。
- 新建或更新后的 Skill 必须包含中文 canonical SKILL.md 与英文 mirror SKILL.en.md。
- SpecLite canonical 和安装副本的 Skill name 与目录名必须以 speclite- 开头。
- 中文 SKILL.md 的章节标题必须使用 English（中文）形式，正文内容使用中文，命令、路径、字段名、fixture 名称、schema/issue id 等技术标识和专有技术术语使用英文。
[Generation Metadata（生成信息）]
本 Skill 由 speclite-skill-creator 自动生成。如需修改，必须同步更新 SKILL.md 与 SKILL.en.md，并同步 assets/source/speclite/support-skills/speclite-skill-lint/ 与实际安装副本。
What ships with it
5 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.
- 10d ago First seen · 51 lines · 80 tokens per session scan A a7554246866f
speclite-skill-lint is a skill published in the GitHub repository flanliulf/SpecLite (4 stars, last pushed 2mo ago), licensed MIT. It adds 80 tokens to every session and 1,148 once invoked, about $0.0004 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.
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…
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…
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…