A command that lists saved project specifications and organizes them by folder or status. A specification is a written plan for a feature, bug fix, or other piece of work.

Use it to filter specs by folder, status, or keyword and sort them by dates, complexity, phases, or task count.

It makes it easier to find planned work and see which items are drafts, active, under review, or completed.

How jnarowski/agentcmd configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to jnarowski/agentcmd. 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/jnarowski/agentcmd/main/.claude/commands/cmd/list-specs.md

Clone the repo

git clone --depth 1 https://github.com/jnarowski/agentcmd

Made for: Claude Code.

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/commands/jnarowski/agentcmd/list-specs/github.svg)](https://agentmods.dev/commands/jnarowski/agentcmd/list-specs)

Your own site

<a href="https://agentmods.dev/commands/jnarowski/agentcmd/list-specs"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/list-specs/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/commands/jnarowski/agentcmd/list-specs"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/list-specs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,939 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.

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.00013	$0.02939
Opus 5.5	$0.00005	$0.01176
Sonnet 5.5	$0.00003	$0.00588
Haiku 4.5	$0.00001	$0.00294

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

Security

Grade A, and why

list-specs 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.

.claude/commands/cmd/list-specs.md · 345 lines

How it starts

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

List Specs

List all specs in the .agent/specs/ directory, organized by workflow folder and optionally filtered by status field. Uses index.json for fast lookups of timestamp ID specs.

Variables

$folder: $1 (optional) - Filter by folder: "backlog", "todo", "done", or "all" (defaults to "all")
$status: $2 (optional) - Filter by status field: "draft", "ready", "in-progress", "review", "completed", or "any" (defaults to "any")
--search: (optional) - Search keyword to fuzzy match in spec names/paths
--sort: (optional) - Sort field: "created", "updated", "id", "complexity", "phases", or "tasks" (defaults to "created")

Instructions

Read index.json for fast lookup of timestamp ID specs
Parse spec files to extract metadata (Status field) only when status filtering is needed
Filter by folder if specified
Filter by status if specified
Search by keyword if specified (fuzzy match in spec names)
Sort results by specified field
Group specs in same folder for multi-spec folders
Display results organized by folder with spec ID, feature name, created/updated dates, and status

Workflow

Load Specs from Index
- Read .agent/specs/index.json
- For each spec in index, extract:
  - Spec ID (key in specs object)
  - Path (contains both location and folder name)
  - Status (cached from spec.md)
  - Created datetime
  - Updated datetime
  - Location: Derive from path by splitting on '/' (e.g., "todo/1-log-streaming" → location="todo", folder="1-log-streaming")
Apply Filters
- Folder filter:
  - If $folder is "backlog": Only show specs where location (from path) is "backlog"
  - If $folder is "todo": Only show specs where location is "todo"
  - If $folder is "done": Only show specs where location is "done"
  - If $folder is "all" or not provided: Show all specs
- Status filter:
  - If $status is specified and not "any":
    - Use cached status from index.json
    - Only include specs matching that status
  - If $status is "any" or not provided: Show all specs
  - If a spec has no status field in index, treat it as status "unknown"

Read the full file on GitHub · 345 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 · 345 lines · 13 tokens per session scan A 291e41fcc789

Subscribe to this mod's changes

list-specs is a command published in the GitHub repository jnarowski/agentcmd (18 stars, last pushed 10mo ago), licensed MIT. It adds 13 tokens to every session and 2,939 once invoked, about $0.0001 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-09-01.

Planning Project management

list-specs next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
list-specsjnarowski/agentcmd	Command	18	10mo ago	MIT	A	13	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

agentcmd: Command for Claude Code