check-docs

A command that checks whether a repository’s documentation is outdated.

In plain words
What is it for?
Use it to scan changed files and run the repository’s documentation-staleness checks without updating the files.
Why use it?
It helps catch documentation that no longer matches recent code or repository changes.

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/dmzoneill/redhat-ai-workflow/check-docs
Clone the repo
git clone --depth 1 https://github.com/dmzoneill/redhat-ai-workflow
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 484 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.00000 $0.00484
Opus 5 $0.00000 $0.00242
Sonnet 5 $0.00000 $0.00097
Haiku 4.5 $0.00000 $0.00048

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

Security

Grade A, and why

check-docs 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.

docs/commands/check-docs.md · 82 lines

What it actually says

/check-docs

Check repository documentation for staleness

Overview

Check repository documentation for staleness

Underlying Skill: update_docs

This command is a wrapper that calls the update_docs skill. For detailed process information, see skills/update_docs.md.

Arguments

No arguments required.

Usage

Examples

skill_run("update_docs", '{"repo": ".", "check_only": true}')
skill_run("update_docs", '{"repo_name": "automation-analytics-backend", "check_only": true}')

Process Flow

This command invokes the update_docs skill. The process flow is:

flowchart LR
    START([User runs /check-docs]) --> VALIDATE[Validate Arguments]
    VALIDATE --> CALL[Call update_docs skill]
    CALL --> EXECUTE[Execute Skill Steps]
    EXECUTE --> RESULT[Return Result]
    RESULT --> END([Complete])

    style START fill:#6366f1,stroke:#4f46e5,color:#fff
    style END fill:#10b981,stroke:#059669,color:#fff
    style CALL fill:#3b82f6,stroke:#2563eb,color:#fff
```text

For detailed step-by-step process, see the [update_docs skill documentation](../skills/update_docs.md).

## Details

## What This Does

1. Scans for changed files in the current branch
2. Checks README.md for broken links
3. Reviews API docs if endpoints changed
4. Checks mermaid diagrams if architecture changed
5. Reports issues and suggestions

## Usage

Run the update_docs skill to check documentation:

```text
skill_run("update_docs", '{"repo": ".", "check_only": true}')
```text

Or for a specific repository:

```text
skill_run("update_docs", '{"repo_name": "automation-analytics-backend", "check_only": true}')

Notes

  • Only runs for repos with docs.enabled=true in config.json
  • Integrated into create_mr and mark_mr_ready skills
  • Use check_only: true to just check, check_only: false for suggestions

(To be determined based on command relationships)

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 · 82 lines · 0 tokens per session scan A fec6d636f0d1

Subscribe to this mod's changes

check-docs is a command published in the GitHub repository dmzoneill/redhat-ai-workflow (5 stars, last pushed 23d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 484 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.