agentmods.dev

devos-docs-refresh

devos-docs-refresh is a command for Claude Code from chhuax/praxis-devos. It costs 0 tokens per session (478 once invoked), scanned A, original, Apache-2.0.

A command for refreshing project documentation so it matches the current code structure and an active OpenSpec change. It can update overview documents, module maps, and surface descriptions.

In plain words
What is it for?
Use it after structural changes or while archiving an OpenSpec change to update project and module documentation.
Why use it?
It prevents documentation from becoming misleading after files, modules, or externally visible behavior change.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: mentions subagents; mentions AGENTS.md.

not rated 21repo 6mo ago A scan 0 tokens original Apache-2.0

Good fit Use it after structural changes or while archiving an OpenSpec change to update project and module documentation.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/chhuax/praxis-devos/devos-docs-refresh
View source ↗ chhuax/praxis-devos
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/chhuax/praxis-devos

Made for: Claude Code.

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 devos-docs-refresh

README.md
[![agentmods](https://agentmods.dev/badge/commands/chhuax/praxis-devos/devos-docs-refresh/github.svg)](https://agentmods.dev/commands/chhuax/praxis-devos/devos-docs-refresh)
Your own site
<a href="https://agentmods.dev/commands/chhuax/praxis-devos/devos-docs-refresh"><img src="https://agentmods.dev/badge/commands/chhuax/praxis-devos/devos-docs-refresh/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 devos-docs-refresh

Your own site · 80×15
<a href="https://agentmods.dev/commands/chhuax/praxis-devos/devos-docs-refresh"><img src="https://agentmods.dev/badge/commands/chhuax/praxis-devos/devos-docs-refresh.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 478 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.00000 $0.00478
Opus 5.5 $0.00000 $0.00191
Sonnet 5.5 $0.00000 $0.00096
Haiku 4.5 $0.00000 $0.00048

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

Security

Grade A, and why

devos-docs-refresh 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.

assets/commands/devos-docs-refresh.md · 76 lines

How it starts

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

devos-docs-refresh

Refresh existing project documentation using the devos-docs skill.

What this does

  • Updates docs/surfaces.yaml when the external surface changes
  • Updates docs/codemaps/project-overview.md to match the current structure
  • Updates module-level codemap docs when structure or responsibilities change
  • Aligns documentation with the current OpenSpec change

Mode

refresh

When to use

Run this command when:

  • code structure has evolved
  • new modules or surfaces have been added
  • existing docs are out of date
  • an OpenSpec change is being archived (REQUIRED)

Change-aware refresh (IMPORTANT)

When invoked during an OpenSpec flow, you MUST provide change context:

  • active changeId
  • OpenSpec artifacts:
    • proposal / design / spec / tasks
  • changed code paths (if available)
  • optional affected module hints

The refresh MUST:

  • reflect actual implemented structure after the change
  • align with spec and design decisions
  • update both:
    • project overview
    • affected module docs

Implementation

  • Invoke the devos-docs skill with mode=refresh

  • Detect artifact_language:

    • prefer docs/surfaces.yaml
    • fallback to AGENTS.md / README.md

  • Pass change-aware context into the skill:

    • REQUIRED for OpenSpec archive / flow-driven refreshes
    • OPTIONAL for general refresh usage outside an active OpenSpec flow

  • Use stable docs routing:

    • docs/surfaces.yaml
    • docs/codemaps/project-overview.md
    • docs/codemaps/module-map.md (multi-module)
    • docs/codemaps/modules/<artifactId>.md (deterministic only)

  • Follow Agent Collaboration protocol if using sub-agent

  • MUST consume sub-agent output (no rebuild from scratch)

  • Validate contract BEFORE writing

  • Write all files in a single pass

Constraints

  • Refresh is incremental (non-destructive)
  • Do not create parallel structures or new CodeMap versions
  • Do not write speculative / future-state content
  • Must align with actual code and OpenSpec spec

Read the full file on GitHub · 76 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. 2mo ago First seen · 76 lines · 0 tokens per session scan A 48b59c761711

Subscribe to this mod's changes

devos-docs-refresh is a command published in the GitHub repository chhuax/praxis-devos (21 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 478 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-30.

Writing and docs
Related

devos-docs-refresh compared with commands from other repositories

devos-docs-refresh next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
devos-docs-refreshchhuax/praxis-devosCommand216mo agoApache-2.0A0Claude 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