status

A read-only command that reports the health of a project's knowledge files and folders.

In plain words
What is it for?
Use it to inspect CLAUDE.md files and summarize document counts and oldest or newest entries in the learnings, patterns, decisions, and research folders.
Why use it?
It makes missing, old, or unexpectedly nested documentation visible without modifying the project.

Command

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 commands/vladolaru/claude-code-plugins/status
Clone the repo
git clone --depth 1 https://github.com/vladolaru/claude-code-plugins
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 788 The whole file, excluding the scripts and references it only reads on demand.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00788
Opus 5 $0.00004 $0.00394
Sonnet 5 $0.00002 $0.00158
Haiku 4.5 $0.00001 $0.00079

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

Security

Grade A, and why

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

plugins/dex/commands/status.md · 88 lines

How it starts

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

/dex:status

Show a read-only knowledge health report for the current project. This command reads and reports — it modifies nothing.

Step 1: Discover Project Infrastructure

Follow the Project Discovery steps from the knowledge-capture skill.

Step 2: Gather Metrics

For each component, gather:

CLAUDE.md:

  • Line count
  • Location (root or .claude/CLAUDE.md)
  • Count of nested CLAUDE.md files (glob for **/CLAUDE.md excluding dependency and build directories — node_modules, vendor, .git, dist, build)

Knowledge directories (for each of learnings/, patterns/, decisions/, research/):

  • Whether the directory exists
  • Number of .md files
  • Most recent file (by filename date prefix YYYY-MM-DD)
  • Oldest file (by filename date prefix)

Step 3: Present Report

Use this exact format:

Project Knowledge Health

CLAUDE.md:        [line_count]/500 lines ([location])
                  [+ N nested CLAUDE.md files, if any]

Learnings:        [count] docs  (.claude/docs/learnings/)
  Latest:         [date] — [title from filename slug]
  Oldest:         [date] — [title from filename slug]

Patterns:         [count] docs  (.claude/docs/patterns/)
  Latest:         [date] — [title from filename slug]
  Oldest:         [date] — [title from filename slug]

Decisions:        [count] docs  (.claude/docs/decisions/)
  Latest:         [date] — [title from filename slug]
  Oldest:         [date] — [title from filename slug]

Research:         [count] docs  (.claude/docs/research/)
  Latest:         [date] — [title from filename slug]
  Oldest:         [date] — [title from filename slug]

Adapt for missing infrastructure:

Condition Report
.claude/docs/ missing "No knowledge directory found. Run /dex:init to set up."
Subdirectory empty "[category]: 0 docs (empty)" — omit Latest/Oldest
Subdirectory missing "[category]: not set up" — omit Latest/Oldest
CLAUDE.md 500+ lines Append warning: "CLAUDE.md is over budget — consider extracting sections."
Migration mismatch detected Append warning: "Knowledge is in .claude/docs/ but project uses AGENTS.md — run /dex:init to migrate to .ai/docs/."

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

  1. 2d ago First seen · 88 lines · 8 tokens per session scan A cb7f53112169

Subscribe to this mod's changes

status is a command published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed 4d ago), licensed MIT. It adds 8 tokens to every session and 788 once invoked, about $0.0000 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-31.