Conductor-Beads: Command for Claude Code

.claude/skills/beads/commands/stats.md

stats is a command for Claude Code from NguyenSiTrung/Conductor-Beads. It costs 5 tokens per session (137 once invoked), scanned A, a copy of stats, Apache-2.0.

A summary command for a Beads project, showing issue counts and progress. It groups issues by status, priority, type, and recent activity.

In plain words
What is it for?
Use it to review completion rate, find blocked issues, check priorities, and decide what work to handle next.
Why use it?
It gives a quick view of project workload and helps reveal blocked work, missing active tasks, or unprioritized issues.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is NguyenSiTrung/Conductor-Beads's own configuration. It tells Claude Code how to work on Conductor-Beads itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Conductor-Beads configures →

Reuse

Borrowing it

Nothing to install: this file belongs to NguyenSiTrung/Conductor-Beads. 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/NguyenSiTrung/Conductor-Beads/main/.claude/skills/beads/commands/stats.md
Clone the repo
git clone --depth 1 https://github.com/NguyenSiTrung/Conductor-Beads

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.

agentmods badge for stats

README.md
[![agentmods](https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/stats/github.svg)](https://agentmods.dev/commands/nguyensitrung/conductor-beads/stats)
Your own site
<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/stats"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-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.

agentmods 80×15 button for stats

Your own site · 80×15
<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/stats"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-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 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00005 $0.00137
Opus 5 $0.00003 $0.00068
Sonnet 5 $0.00001 $0.00027
Haiku 4.5 $0.00001 $0.00014

Measured 9d ago against content hash f4da8a61fb79, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 9d 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

This is a copy

100% identical to stats — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/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.

  1. 9d 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 NguyenSiTrung/Conductor-Beads (24 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 5 tokens to every session and 137 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to stats, differing in 0 lines, and is treated as a copy.