ai-workspace-generator: Command for Claude Code

.claude/commands/aiws-doc-sync.md

aiws-doc-sync is a command for Claude Code from grojof/ai-workspace-generator. It costs 17 tokens per session (219 once invoked), scanned A, original, Apache-2.0.

A command for refreshing living project documentation about the current state, architecture, decisions, and development changes.

In plain words
What is it for?
It reviews recent Git changes and updates the project state, module map, architecture diagrams, change summaries, and declared project documentation while preserving manual notes.
Why use it?
It prevents the project's reference documents from becoming outdated as code and decisions change.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is grojof/ai-workspace-generator's own configuration. It tells Claude Code how to work on ai-workspace-generator itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-workspace-generator configures →

Reuse

Borrowing it

Nothing to install: this file belongs to grojof/ai-workspace-generator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/grojof/ai-workspace-generator/main/.claude/commands/aiws-doc-sync.md
Clone the repo
git clone --depth 1 https://github.com/grojof/ai-workspace-generator

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 aiws-doc-sync

README.md
[![agentmods](https://agentmods.dev/badge/commands/grojof/ai-workspace-generator/aiws-doc-sync/github.svg)](https://agentmods.dev/commands/grojof/ai-workspace-generator/aiws-doc-sync)
Your own site
<a href="https://agentmods.dev/commands/grojof/ai-workspace-generator/aiws-doc-sync"><img src="https://agentmods.dev/badge/commands/grojof/ai-workspace-generator/aiws-doc-sync/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 aiws-doc-sync

Your own site · 80×15
<a href="https://agentmods.dev/commands/grojof/ai-workspace-generator/aiws-doc-sync"><img src="https://agentmods.dev/badge/commands/grojof/ai-workspace-generator/aiws-doc-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 219 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.00017 $0.00219
Opus 5 $0.00009 $0.00110
Sonnet 5 $0.00003 $0.00044
Haiku 4.5 $0.00002 $0.00022

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

Security

Grade A, and why

aiws-doc-sync 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 9d 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/commands/aiws-doc-sync.md · 18 lines

What it actually says

/aiws-doc-sync

Update the project's living documentation so any agent gets accurate context cheaply.

  1. Scan recent changes (git status/log, modified modules).
  2. Update docs/development/status/PROJECT-STATE.md: overview, module map, decisions log, current status.
    • If SDD is active, summarize the state of each folder under docs/development/changes/*.
  3. Update docs/development/status/ARCHITECTURE.md: keep Mermaid diagrams current (architecture, data flow, module deps).
  4. Review the project docs under docs/project/ (the docs declared in the docs.contract config): keep them accurate and free of dangling references / orphans (ai-workspace doctor flags these).
  5. Only rewrite content inside ai-workspace:begin/end markers; preserve manual notes outside them.

Keep it concise — this file is read often; favor a compact, scannable snapshot over prose.

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. 9d ago First seen · 18 lines · 17 tokens per session scan A fa8f9bed003f

Subscribe to this mod's changes

aiws-doc-sync is a command published in the GitHub repository grojof/ai-workspace-generator (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 219 once invoked, about $0.0001 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.