agentistics: Command for Claude Code

.claude/commands/update-docs.md

update-docs is a command for Claude Code from blpsoares/agentistics. It costs 0 tokens per session (481 once invoked), scanned A, original, MIT.

A documentation-update workflow that compares project documentation with the source code and revises only outdated parts. It also runs a TypeScript type check afterward.

In plain words
What is it for?
Use it to refresh architecture, setup, data-source, metrics, API, and package documentation.
Why use it?
It helps prevent README files and technical guides from describing behavior the code no longer has.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is blpsoares/agentistics's own configuration. It tells Claude Code how to work on agentistics 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 agentistics configures →

Reuse

Borrowing it

Nothing to install: this file belongs to blpsoares/agentistics. 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/blpsoares/agentistics/main/.claude/commands/update-docs.md
Clone the repo
git clone --depth 1 https://github.com/blpsoares/agentistics

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 update-docs

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/blpsoares/agentistics/update-docs"><img src="https://agentmods.dev/badge/commands/blpsoares/agentistics/update-docs.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 481 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.00481
Opus 5.5 $0.00000 $0.00192
Sonnet 5.5 $0.00000 $0.00096
Haiku 4.5 $0.00000 $0.00048

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

Security

Grade A, and why

update-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 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.

.claude/commands/update-docs.md · 43 lines

What it actually says

/update-docs

Update all documentation in this project to reflect the current state of the codebase.

What to do

  1. Read every markdown file listed below
  2. Read the actual source files they reference to verify what's still true
  3. Rewrite only what's outdated — preserve accurate content and existing structure
  4. Run bun tsc --noEmit at the end to confirm nothing broke

Files to update (in priority order)

File Covers
CLAUDE.md Developer instructions for AI assistants — most critical
README.md Project overview, features, install steps
docs/architecture.md System architecture and data flow
docs/data-sources.md Data sources and processing logic
docs/metrics.md Metrics tracked and how they're calculated
docs/mcp.md MCP server tools and usage
docs/nay.md Nay agent documentation
docs/opentelemetry.md OpenTelemetry export
packages/mcp/README.md MCP package standalone readme

Key things to check

  • Monorepo structure: does the doc list all packages (core, server, web, mcp, desktop)?
  • Calculation functions: are calcCost, getModelPrice, MODEL_PRICING correctly attributed to @agentistics/core?
  • files_modified: is it documented that this now counts Edit/Write/MultiEdit tool calls (not just git)?
  • git.ts workspace fallback: documented that non-git project dirs scan subdirs?
  • PWA: mentioned in features/architecture?
  • Settings modal: unified tabbed modal (Preferences / Live / Install / Environment)?
  • Chat sounds: chatSounds.ts with 5 synthesized tones?
  • MCP tools: all 11 tools listed and accurately described?

Rules

  • CLAUDE.md must be kept precise — it's read by AI assistants on every session
  • Don't add content that isn't true yet (e.g. desktop app is in-progress, not shipped)
  • Don't change tone or add emojis
  • When in doubt about whether something changed, read the source file
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 · 43 lines · 0 tokens per session scan A 513fb9609a25

Subscribe to this mod's changes

update-docs is a command published in the GitHub repository blpsoares/agentistics (44 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 481 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-09-01.

Related

update-docs compared with commands from other repositories

update-docs next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
update-docsblpsoares/agentisticsCommand441mo agoMITA0Claude Code
templategastownhall/beadsCommand29kyesterdayMITA0Claude Code
auto-browsemarcusquinn/aidevopsCommand439todayMITA18Claude Code
telemetry-queryJackScammell/Parliament-Of-ChaosCommand49d agoMITA19Claude Code
doctorfatihkan/badiCommand71mo agoMITA0Claude Code
fixstefan-jansen/claude-code-toolkitCommand924mo agoMITA9Claude Code
draft-planAcKeskin/contextureCommand22d agoMITA70Claude Code