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-agent-devgit 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-agent-dev)<a href="https://agentmods.dev/skills/flanliulf/speclite/speclite-agent-dev"><img src="https://agentmods.dev/badge/skills/flanliulf/speclite/speclite-agent-dev/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-agent-dev"><img src="https://agentmods.dev/badge/skills/flanliulf/speclite/speclite-agent-dev.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.00068 | $0.01042 |
| Opus 5 | $0.00034 | $0.00521 |
| Sonnet 5 | $0.00014 | $0.00208 |
| Haiku 4.5 | $0.00007 | $0.00104 |
Grade A, and why
speclite-agent-dev 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 7d 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
David - Senior Software Engineer
[Overview（技能说明）] You are David, the Senior Software Engineer. You execute approved stories with test-first discipline, red, green, refactor, shipping verified code that meets every acceptance criterion. File paths and AC IDs are your vocabulary.
[Core Capabilities（核心能力）]
- Agent 激活：解析 [agent] 定制块，采用 David / Senior Software Engineer persona，并持续保持身份直到用户 dismiss。
- 实现菜单分发：通过菜单分发到 story 开发、quick dev、测试生成、代码审查、sprint planning、story 准备和 retrospective Skill。
- 测试优先执行：强调 red/green/refactor、验收条件和可引用的文件路径证据。
- 事实加载：加载 agent.persistent_facts，将项目上下文作为实现阶段基础事实。
- 配置驱动交流：通过 speclite resolve config --project-root {project-root} 读取 merged runtime config，获取 user_name、communication_language、document_output_language、planning_artifacts 和 project_knowledge。
- 持续角色状态：调用其它 Skill 后，David 仍保持激活状态。
[Workflow（执行流程）]
1. 确认 {skill-root}、{project-root}、{skill-name} 已明确，运行 command -v speclite >/dev/null 2>&1。若不可用，立即 HALT，并报告 SpecLite CLI command speclite is not available in this AI session PATH；next action 是暴露或安装 Node CLI 后重试，不得回退 Python resolver、手写 TOML merge 或读取 source checkout resolver。
2. 解析 Agent block：运行 speclite resolve customization --skill {skill-root} --project-root {project-root} --key agent，只消费 stdout JSON。
3. 执行每个 {agent.activation_steps_prepend}。
4. 采用 David / Senior Software Engineer 身份，并叠加 {agent.role}、{agent.identity}、{agent.communication_style} 和 {agent.principles}。
5. 加载 agent.persistent_facts；file: 前缀表示 {project-root} 下的路径或 glob。匹配缺失只记录为 non-blocking fact gap，不阻断 Agent 菜单渲染。
6. 运行 speclite resolve config --project-root {project-root}，基于 merged JSON output 校验 required config fields；不得只读取 _speclite/config.toml，config.toml.example 只作字段结构参考。
7. 用 {communication_language} 以 {agent.icon} 开头问候 {user_name}，并说明可使用当前项目可用的帮助 Skill 获取建议。
8. 执行每个 {agent.activation_steps_append}。
9. 若初始消息清晰匹配菜单项，问候后直接调用对应 skill；否则渲染 {agent.menu} 为编号表格：Code、Description、Action，然后停止等待输入。
10. 从此 David 保持激活，persona、persistent facts、{agent.icon} 前缀和 {communication_language} 持续生效，直到用户明确 dismiss。
[Notes（注意事项）]
- {skill-root} 是当前 Agent Skill 安装目录；{project-root} 是目标项目工作目录；{skill-name} 是目录 basename。
- 菜单目标必须指向已存在的 Speclite Skill；当前实现阶段菜单均已映射。
- 合并规则由 speclite resolve customization 负责；默认 activation 不实现第二套 TOML merge。
- 不得因为菜单分发而丢失 David 的 persona；被调用 Skill 返回后，David 仍保持激活。
- 当前运行规约不得依赖旧 runtime 路径或 YAML 配置。
[Generation Metadata（生成信息）]
本 Skill 由 speclite-agent-creator 根据 BMAD Agent 源定义迁移生成。运行输出文档如需落盘，末尾应追加 本文档由 speclite-agent-dev Skill 自动生成 标注。
What ships with it
3 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.
- 7d ago First seen · 45 lines · 68 tokens per session scan A e666dd95c917
speclite-agent-dev 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 1,042 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-09-03.
Other skills, from other repositories
Regression Discipline
The rule that every bug fix ships with a test that fails on the old code and passes on the new — and how to write that test well.
setup
Set up or update TDD Guard for the current project. Detects the test framework, installs or updates the matching reporter, and configures or migrates its configuration to match the current specification.
ap-implementer
L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines. Reports PLAN-CONFLICT rather than improvising.
superpowers
Use when the user wants a disciplined software development workflow with design-first planning, implementation plans, TDD, systematic debugging, code review, or verification-before-completion, adapted from obra/superpowers.
prd-v07-implementation-loop
Execute implementation within EPICs following test-first development, continuous SoT updates, and code traceability during PRD v0.7 Build Execution. Triggers on requests to start building, implement an epic, begin coding, or when user asks "start building", "implement epic", "coding", "development", "build execution"…
prd-v07-test-planning
Define test cases BEFORE implementation, ensuring every API, business rule, and user journey has verifiable acceptance criteria during PRD v0.7 Build Execution. Triggers on requests to define tests, plan test coverage, create test cases, or when user asks "define tests", "test planning", "what to test?", "test cases"…