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 agentmods add skills/codervisor/leanspec/leanspec-developmentnpx skills add codervisor/leanspec --skill leanspec-developmentgit clone --depth 1 https://github.com/codervisor/leanspecWhat 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 | $0.00144 | $0.02657 |
| Opus 5 | $0.00072 | $0.01328 |
| Sonnet 5 | $0.00029 | $0.00531 |
| Haiku 4.5 | $0.00014 | $0.00266 |
Grade A, and why
leanspec-development 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 2d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LeanSpec Development Skill
Unified guide for all LeanSpec development: coding, commands, publishing, CI/CD, and runner research.
Quick Navigation
| Goal | Reference |
|---|---|
| Mandatory rules & conventions | RULES.md |
| Changelog format & workflow | Changelog (below) |
| i18n file locations & patterns | I18N.md |
| Monorepo structure & packages | STRUCTURE.md |
| Full release checklist | PUBLISHING.md |
| npm distribution architecture | NPM-DISTRIBUTION.md |
| Dev publishing workflow | DEV-PUBLISHING.md |
| CI workflow details | CI-WORKFLOWS.md |
| gh CLI command reference | CI-COMMANDS.md |
| CI troubleshooting | CI-TROUBLESHOOTING.md |
| Runner ecosystem catalog | runners-catalog.md |
Core Principles
- Use pnpm — Never npm or yarn
- DRY — Extract shared logic, avoid duplication
- Test What Matters — Business logic and data integrity, not presentation
- Leverage Turborepo — Smart caching (19s → 126ms builds)
- i18n is MANDATORY — Every user-facing string needs both en AND zh-CN (see I18N.md)
- Follow Rust Quality — All code must pass
cargo clippy -- -D warnings
Commands
Daily Development
pnpm install # Install dependencies
pnpm dev # Start web UI + Rust HTTP server
pnpm dev:watch # Same + auto-rebuild Rust on changes
pnpm dev:web # Start web UI only
pnpm dev:desktop # Start desktop app
pnpm build # Build all TS packages
pnpm build:rust # Build Rust (debug)
pnpm build:rust:release # Build Rust (release)
pnpm typecheck # ← NEVER SKIP before marking work complete
pnpm test # Run all tests
pnpm test:watch # Watch mode
pnpm test:coverage # With coverage
pnpm test:rust # Rust tests only
pnpm format # Format all code
pnpm cli # Run LeanSpec CLI
What ships with it
10 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.
- references/CI-COMMANDS.md 5.9 KB
- references/CI-TROUBLESHOOTING.md 5.3 KB
- references/CI-WORKFLOWS.md 6.5 KB
- references/DEV-PUBLISHING.md 2.5 KB
- references/I18N.md 2.0 KB
- references/NPM-DISTRIBUTION.md 6.1 KB
- references/PUBLISHING.md 6.7 KB
- references/RULES.md 11 KB
- references/runners-catalog.md 4.2 KB
- references/STRUCTURE.md 6.1 KB
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.
- 2d ago First seen · 285 lines · 144 tokens per session scan A d7cf85c76604
leanspec-development is a skill published in the GitHub repository codervisor/leanspec (287 stars, last pushed 3mo ago), licensed MIT. It adds 144 tokens to every session and 2,657 once invoked, about $0.0007 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-30.
Other skills, from other repositories
add-community-extension
Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension…
github-workflows
Work with GitHub Actions CI/CD workflows - read live syntax, monitor runs, and debug failures. Use when writing, running, or debugging GitHub Actions workflows.
comet-github-ci-triage
使用 PR 当前准确 head、失败 job 日志、本地复现边界和可合并状态，诊断 Comet PR 的 GitHub Actions 与覆盖率检查。PR 出现 CI 报错、Codecov 问题、过期检查或无法解释的红色 job 时使用。.
aiox-devops
Activate Gage (devops) for GitHub Repository Manager & DevOps Specialist. Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized to push to remote repository.
qa-ci-cd-testing
当需要把测试集成到 CI/CD 流水线中、或者现有流水线的测试环节跑起来效率低不可靠时使用此技能。覆盖流水线各阶段的分层测试卡点设计（提交检查→单元测试→接口测试→UI 测试→回归测试）、工具集成策略和质量门禁配置。不要在 CI 里堆满慢的 UI 测试——而是构建测试金字塔：提交阶段跑最快的（<5min），合码阶段跑核心的（<15min），夜间跑全量的。.
qa-test-automation-arch
当需要设计自动化测试框架、或者现有框架维护成本太高需要重构时使用此技能。运用 PageObject、分层测试、关键字驱动、数据驱动等模式设计可维护可扩展的自动化架构。不要直接写测试代码——先设计架构：选型（UI/API/单元）、分层（测试层/业务层/基础设施层）、数据管理（测试数据与脚本分离）和 CI 集成方案。好的自动化架构应该让写用例的人不需要懂底层实现。.