A command that summarizes project issue statistics and progress, including counts by status, priority, and type, completion rate, and recently updated issues.

Review project metrics, identify blocked or unstarted work, and decide whether to investigate blockers, find ready tasks, or reprioritize open issues.

It gives you a quick view of project workload and progress without inspecting every issue individually.

stats — Command for Claude Code by gastownhall/beads

About the project

gastownhall/beads is a command-line graph issue tracker that gives coding agents persistent, structured memory through a dependency-aware task database. It is for developers and AI agents handling long-running work across tasks, branches, and sessions. The catalogue entries provide integrations and workflows for operating Beads with coding agents.

gastownhall/beads · 28,536 stars · on GitHub · beads.gascity.com

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.

Clone the repo

git clone --depth 1 https://github.com/gastownhall/beads

Made for: Claude Code.

Or install beads, the plugin that ships this one along with the rest of its 29 commands, 4 hooks.

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/gastownhall/beads/stats/github.svg)](https://agentmods.dev/commands/gastownhall/beads/stats)

Your own site

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

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

When invoked 137 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.00005	$0.00137
Opus 5.5	$0.00002	$0.00055
Sonnet 5.5	$0.00001	$0.00027
Haiku 4.5	$0.00001	$0.00014

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

Security

Grade A, and why

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

stats — 100% identical, 0 lines differ

plugins/beads/skills/beads/commands/stats.md · 18 lines

What it actually says

Display statistics about the current beads project.

Use the beads MCP stats tool to retrieve project metrics and present them clearly:

Total issues by status (open, in_progress, blocked, closed)
Issues by priority level
Issues by type (bug, feature, task, epic, chore)
Completion rate
Recently updated issues

Optionally suggest actions based on the stats:

High number of blocked issues? Run /beads:blocked to investigate
No in_progress work? Run /beads:ready to find tasks
Many open issues? Consider prioritizing with /beads:update

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 · 18 lines · 5 tokens per session scan A f4da8a61fb79

Subscribe to this mod's changes

stats is a command published in the GitHub repository gastownhall/beads (28,536 stars, last pushed yesterday), licensed MIT. It adds 5 tokens to every session and 137 once invoked, about $0.0000 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.

Analytics and metrics Claude Code Project management agents coding

stats next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
statsgastownhall/beads	Command	29k	yesterday	MIT	A	5	Claude Code
lavra-work-teamsroberto-mello/lavra	Command	53	15d ago	MIT	A	22	Claude Code
lavra-retroroberto-mello/lavra	Command	53	15d ago	MIT	A	17	Claude Code
lavra-work-ralphroberto-mello/lavra	Command	53	15d ago	MIT	A	27	Claude Code
lavra-shiproberto-mello/lavra	Command	53	15d ago	MIT	A	21	Claude Code
lavra-quickroberto-mello/lavra	Command	53	15d ago	MIT	A	16	Claude Code
lavra-recallroberto-mello/lavra	Command	53	15d ago	MIT	A	14	Claude Code