standards-status

standards-status is a command for Claude Code from wqaetly/claude-code-plugins. It costs 0 tokens per session (1,501 once invoked), scanned A, original, no licence file.

A project command that shows the Claude development standards currently loaded, whether they are active, and their usage statistics.

In plain words
What is it for?
Checking loaded standards, activation status, and related usage information.
Why use it?
It makes the current standards state visible when you need to confirm which instructions are affecting development work.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the claude-standards plugin — 4 commands shipped together

Good fit Checking loaded standards, activation status, and related usage information.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/wqaetly/claude-code-plugins/standards-status
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/wqaetly/claude-code-plugins

Made for: Claude Code.

Or install claude-standards, the plugin that ships this one along with the rest of its 4 commands.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/wqaetly/claude-code-plugins/standards-status/github.svg)](https://agentmods.dev/commands/wqaetly/claude-code-plugins/standards-status)
Your own site
<a href="https://agentmods.dev/commands/wqaetly/claude-code-plugins/standards-status"><img src="https://agentmods.dev/badge/commands/wqaetly/claude-code-plugins/standards-status/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 standards-status

Your own site · 80×15
<a href="https://agentmods.dev/commands/wqaetly/claude-code-plugins/standards-status"><img src="https://agentmods.dev/badge/commands/wqaetly/claude-code-plugins/standards-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,501 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 unknown 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.1 $0.00000 $0.01501
Opus 5.5 $0.00000 $0.00600
Sonnet 5.5 $0.00000 $0.00300
Haiku 4.5 $0.00000 $0.00150

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

Security

Grade A, and why

standards-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 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-standards/commands/standards-status.md · 241 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2mo ago First seen · 241 lines · 0 tokens per session scan A ccd091e334d9

Subscribe to this mod's changes

standards-status is a command published in the GitHub repository wqaetly/claude-code-plugins (5 stars, last pushed 1y ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,501 tokens. 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.

Related

standards-status compared with commands from other repositories

standards-status next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
standards-statuswqaetly/claude-code-pluginsCommand51y agononeA0Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code