What is leanspec-dev-process?

A spec-driven development process for making non-trivial changes through a GitHub issue, branch, implementation, pull request, merge, and closure. Spec-driven development means writing the change requirements before building it.

Use it to start work on lean-spec, create or follow issue-based specifications, implement changes on branches, connect pull requests to their specs, and close completed work.

It gives each change a traceable path from request to merged code and makes the repository's development rules clear.

How codervisor/leanspec configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to codervisor/leanspec. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/codervisor/leanspec/main/.agents/skills/leanspec-dev-process/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/codervisor/leanspec

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/codervisor/leanspec/leanspec-dev-process/github.svg)](https://agentmods.dev/skills/codervisor/leanspec/leanspec-dev-process)

Your own site

<a href="https://agentmods.dev/skills/codervisor/leanspec/leanspec-dev-process"><img src="https://agentmods.dev/badge/skills/codervisor/leanspec/leanspec-dev-process/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/codervisor/leanspec/leanspec-dev-process"><img src="https://agentmods.dev/badge/skills/codervisor/leanspec/leanspec-dev-process.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 160 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,983 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Agent Snooping · line 169
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
medium Agent Snooping · line 174
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00160	$0.02983
Opus 5.5	$0.00064	$0.01193
Sonnet 5.5	$0.00032	$0.00597
Haiku 4.5	$0.00016	$0.00298

Measured 2mo ago against content hash 26c2e6dd5b2a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

leanspec-dev-process 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 2mo 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.

.agents/skills/leanspec-dev-process/SKILL.md · 179 lines

How it starts

The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.

leanspec-dev-process

The spec-issue-driven development (SDD) loop on lean-spec. Every non-trivial change starts as a GitHub spec issue on codervisor/leanspec, proceeds through a PR that references it, and closes when the PR merges.

Lean-spec is its own dogfood: we use the SDD loop we ship. The historical specs/ directory is frozen as a snapshot of pre-migration work; new specs are GitHub issues. This is the same shape as Onsager's and Duhem's loops — the area taxonomy and toolchain checks are lean-spec-specific.

The loop

     ┌─────────────────────────────────────────────────────────────────┐
     │                                                                 │
     │   idea/request                                                  │
     │        ↓                                                        │
     │   spec(<area>): ...    ← issue-spec skill                       │
     │        │                                                        │
     │        ↓                                                        │
     │   branch + implement                                            │
     │        │                                                        │
     │        ↓                                                        │
     │   leanspec-pre-push    ← merge preview, typecheck, test, clippy │
     │        │                                                        │
     │        ↓                                                        │
     │   git push → open PR (body: "Closes #N" or "Part of #N")        │
     │        │                                                        │
     │        ↓                                                        │
     │   leanspec-pr-lifecycle   ← CI triage, review, iterate          │
     │        │                                                        │
     │        ↓                                                        │
     │   merge                                                         │
     │        │                                                        │
     │        │ Closes #N → GitHub auto-closes spec                    │
     │        │ Part of #N → tick Plan items manually (pr-lifecycle)   │
     │        ↓                                                        │
     │   spec closed (Closes) OR Plan items ticked (Part of)           │
     │                                                                 │
     └─────────────────────────────────────────────────────────────────┘

Read the full file on GitHub · 179 lines

Changes

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.

2mo ago First seen · 179 lines · 160 tokens per session scan A 26c2e6dd5b2a

Subscribe to this mod's changes

leanspec-dev-process is a skill published in the GitHub repository codervisor/leanspec (300 stars, last pushed 5mo ago), licensed MIT. It adds 160 tokens to every session and 2,983 once invoked, about $0.0006 per session on Opus 5.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.

Git and workflow Planning Project Management ai ai-agents development spec spec-driven-development

leanspec-dev-process next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
leanspec-dev-processcodervisor/leanspec	Skill	300	5mo ago	MIT	A	160	Claude Code, Codex
add-community-extensiongithub/spec-kit	Skill	148k	yesterday	MIT	A	63	Claude Code
ax-extract-workflowsickn33/agentic-awesome-skills	Skill	49k	yesterday	MIT	A	35	Claude Code
gsd-quickopen-gsd/gsd-core	Skill	11k	yesterday	MIT	A	24	Claude Code
gsd-quick-batchopen-gsd/gsd-core	Skill	11k	yesterday	MIT	A	32	Claude Code
gsd-workspaceopen-gsd/gsd-core	Skill	11k	yesterday	MIT	A	20	Claude Code
gsd-inboxopen-gsd/gsd-core	Skill	11k	yesterday	MIT	A	23	Claude Code

leanspec: Skill for Claude Code