What is claudemd-status?

A command that reports the installed claudemd plugin version, specification version, kill-switch state and rule-hit summary. A kill switch is a setting that disables a hook or other enforcement check.

Use it to check plugin status, diagnose an installation that has not completed, view hook-disabling environment variables and inspect bypass-token details with verbose output.

It helps determine whether the plugin is installed and current, whether its checks are disabled and what may need fixing after an update.

claudemd-status — Command for Claude Code by sdsrss: A command that reports the installed claudemd plugin version…

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add sdsrss/claudemd

Claude Code

/plugin install claudemd

Made for: Claude Code.

Or install claudemd, the plugin that ships this one along with the rest of its 16 commands, 6 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/sdsrss/claudemd/claudemd-status.svg)](https://agentmods.dev/commands/sdsrss/claudemd/claudemd-status)

Your own site

<a href="https://agentmods.dev/commands/sdsrss/claudemd/claudemd-status"><img src="https://agentmods.dev/badge/commands/sdsrss/claudemd/claudemd-status.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 387 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.

Model	Per session	Once invoked
Fable 5.1	$0.00038	$0.00387
Opus 5	$0.00019	$0.00193
Sonnet 5	$0.00008	$0.00077
Haiku 4.5	$0.00004	$0.00039

Measured yesterday against content hash 1f343d5f1a47, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

claudemd-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 yesterday.

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.

commands/claudemd-status.md · 13 lines

What it actually says

Run: node ${CLAUDE_PLUGIN_ROOT}/scripts/status.js (no flag) for the default summary, or node ${CLAUDE_PLUGIN_ROOT}/scripts/status.js --verbose when the user wants the full kill-switch + escape-token table.

Surface the JSON output as a human-readable summary.

If plugin.installed is false and plugin.hint == "cache-present-bootstrap-pending": tell the user the plugin is staged on disk (list plugin.cacheVersions) but install.js has not run yet — Claude Code does not fire postInstall, so either start a fresh Claude Code session (the SessionStart hook bootstraps it) or run node ~/.claude/plugins/cache/claudemd/claudemd/<latest-version>/scripts/install.js now.
If plugin.installed is false and no hint is set: suggest /plugin marketplace add sdsrss/claudemd followed by /plugin install claudemd@claudemd.
When --verbose is passed: the JSON includes a verbose block with verbose.killSwitches.perHook (env var name + event + effective vs persisted state for every shipped hook), verbose.killSwitches.subFeature (toggles that silence one feature of a hook without disabling the hook), and verbose.escapeTokens (every per-invocation bypass token with its target hook + spec section — read the count off the list rather than quoting one here). Use this when the user asks "which env var disables hook X" or "what's the bypass token for §Y" without having them grep README.

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.

yesterday Changed 1f343d5f1a47
6d ago First seen · 13 lines · 38 tokens per session scan A 8632409893ca

Subscribe to this mod's changes

claudemd-status is a command published in the GitHub repository sdsrss/claudemd (2 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 387 once invoked, about $0.0002 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.

claude-code claude-code-plugin code-quality commit-lint hooks npm-cli

claudemd-status

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

plan

simplify

audit

test

git

edit