What is leanspec AGENTS.md?

A guide for LeanSpec, a lightweight method for planning software work with written specifications. It explains how the project uses GitHub issues as its current source of truth for specs.

Use it when starting non-trivial LeanSpec work, writing an issue specification, choosing a development process, or checking the project’s rules for frozen historical specs.

It clarifies when work needs a written plan, how to structure that plan, and how to connect it to a branch and pull request. This prevents significant changes from starting without agreement on the design and tests.

leanspec AGENTS.md — Instructions file by codervisor

Install

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.

agentmods

npx agentmods add instructions/codervisor/leanspec/agents-md

Clone the repo

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

Made for: Codex, OpenCode.

Per session 984 This file is loaded in full into every session.

When invoked 984 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

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	$0.00984	$0.00984
Opus 5	$0.00492	$0.00492
Sonnet 5	$0.00197	$0.00197
Haiku 4.5	$0.00098	$0.00098

Measured 2d ago against content hash da59cedc9490, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

leanspec AGENTS.md 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.

AGENTS.md · 62 lines

How it starts

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

AI Agent Instructions

Project: LeanSpec

Lightweight spec methodology for AI-powered development.

Skills

This project uses the Agent Skills framework for domain-specific guidance. Read the appropriate skill when working on related tasks.

Spec-driven development (GitHub-issue specs)

Lean-spec dogfoods its own SDD methodology with GitHub issues as the canonical spec medium. The specs/ directory is a frozen historical snapshot — new specs are GitHub issues on codervisor/leanspec. A pre-commit hook and CI job (freeze-specs) block additions/modifications under specs/; see specs/FROZEN.md.

leanspec-dev-process - End-to-end SDD loop (spec → branch → PR → merge)
- Location: .agents/skills/leanspec-dev-process/SKILL.md
- Use when: Starting non-trivial work, deciding spec-vs-trivial, picking branch name
- Key: No PR without a spec issue or trivial label
issue-spec - Create lean-spec style GitHub issue specs
- Location: .agents/skills/issue-spec/SKILL.md
- Use when: Asked to "spec this" or planning work that needs alignment
- Key: Body under ~2000 tokens; Overview / Design / Plan / Test / Provider impact / Alignment / Notes
leanspec-pre-push - Pre-push checks (sync main, typecheck, clippy, spec-link)
- Location: .agents/skills/leanspec-pre-push/SKILL.md
- Use when: About to git push, hitting merge conflicts, "ready to push"
- Key: CI tests a merge preview, not the branch alone — always sync main first
leanspec-pr-lifecycle - Manage PR post-push (CI triage, review, label flips, merge)
- Location: .agents/skills/leanspec-pr-lifecycle/SKILL.md
- Use when: CI is failing, review comments arrive, PR needs label flip, merge follow-through
- Key: Use mcp__github__* for issue/PR mutation; never gh CLI for that

Read the full file on GitHub · 62 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.

2d ago First seen · 62 lines · 984 tokens per session scan A da59cedc9490

Subscribe to this mod's changes

leanspec AGENTS.md is an instructions file published in the GitHub repository codervisor/leanspec (287 stars, last pushed 3mo ago), licensed MIT. It adds 984 tokens to every session, about $0.0049 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.

Planning Project Management Project management Writing and docs ai ai-agents development spec spec-driven-development

leanspec AGENTS.md

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

AI Agent Instructions

Project: LeanSpec

Skills

Spec-driven development (GitHub-issue specs)

What this file has done since we first saw it

Other instructions, from other repositories

spec-kit AGENTS.md

FlowBoard AGENTS.md

AllBeads CLAUDE.md

claude-sdd-planner AGENTS.md

mcp-redmine-rest CLAUDE.md

vibe-garden CLAUDE.md