doc-status

doc-status is a command for Claude Code from arimxyer/doc-manager-mcp. It costs 4 tokens per session (272 once invoked), scanned A, original, MIT.

A command for a quick check of a project's documentation health and synchronization status.

In plain words
What is it for?
Use it to check initialization, changed files, affected documentation, last synchronization, and whether the project needs a documentation sync or quality review.
Why use it?
It quickly shows whether documentation may be out of date after code changes, without requiring a full review.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the doc-manager plugin — 3 skills, 4 commands, 2 agents, 1 hook, 1 MCP server shipped together

Good fit Use it to check initialization, changed files, affected documentation, last synchronization, and whether the project needs a documentation sync or quality review.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/arimxyer/doc-manager-mcp/doc-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/arimxyer/doc-manager-mcp

Made for: Claude Code.

Or install doc-manager, the plugin that ships this one along with the rest of its 3 skills, 4 commands, 2 agents, 1 hook, 1 MCP server.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/arimxyer/doc-manager-mcp/doc-status.svg)](https://agentmods.dev/commands/arimxyer/doc-manager-mcp/doc-status)
Your own site
<a href="https://agentmods.dev/commands/arimxyer/doc-manager-mcp/doc-status"><img src="https://agentmods.dev/badge/commands/arimxyer/doc-manager-mcp/doc-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 4 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 272 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00004 $0.00272
Opus 5 $0.00002 $0.00136
Sonnet 5 $0.00001 $0.00054
Haiku 4.5 $0.00000 $0.00027

Measured 7d ago against content hash 9f6dfac5acae, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

doc-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 7d 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.

plugin/commands/doc-status.md · 49 lines

What it actually says

Quick Documentation Status Check

Run a quick documentation health check for the current project.

doc-expert agent Please provide a quick documentation status check.

This should include:

  1. Detect if doc-manager is initialized (check for .doc-manager/)
  2. If initialized, run docmgr_detect_changes to check for changes since last sync
  3. Report brief summary:
    • Project platform
    • Number of changed files
    • Affected documentation files
    • Sync status (in_sync | out_of_sync | unknown)

Format the output concisely:

## Documentation Status

**Platform**: {platform}
**Last Sync**: {timestamp or "unknown"}

### Quick Stats
- Changed Files: {count}
- Affected Docs: {count}

### Status: {in_sync | out_of_sync | not_initialized}

### Quick Actions
- /doc-sync - Sync with code changes
- /doc-quality - Full quality assessment

If not initialized:

## Documentation Status

**Status**: Not initialized

### Setup
Run `doc-expert agent Set up documentation management` to initialize.
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. 7d ago First seen · 49 lines · 4 tokens per session scan A 9f6dfac5acae

Subscribe to this mod's changes

doc-status is a command published in the GitHub repository arimxyer/doc-manager-mcp (6 stars, last pushed 7mo ago), licensed MIT. It adds 4 tokens to every session and 272 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.