Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Marcel-Bich/marcel-bich-claude-marketplace/plugin install dogmaWrote 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.
[](https://agentmods.dev/commands/marcel-bich/marcel-bich-claude-marketplace/docs-update)<a href="https://agentmods.dev/commands/marcel-bich/marcel-bich-claude-marketplace/docs-update"><img src="https://agentmods.dev/badge/commands/marcel-bich/marcel-bich-claude-marketplace/docs-update/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.
<a href="https://agentmods.dev/commands/marcel-bich/marcel-bich-claude-marketplace/docs-update"><img src="https://agentmods.dev/badge/commands/marcel-bich/marcel-bich-claude-marketplace/docs-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00011 | $0.04528 |
| Opus 5 | $0.00005 | $0.02264 |
| Sonnet 5 | $0.00002 | $0.00906 |
| Haiku 4.5 | $0.00001 | $0.00453 |
Grade A, and why
docs-update 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 669 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude-Dogma: Documentation Update
You are executing the /dogma:docs-update command. Your task is to synchronize documentation across README files and wiki articles, ensuring everything is up-to-date.
Overview
This command:
- Locates the wiki repository (parallel checkout, or clone from URL)
- Analyzes changes in the main repo that affect documentation
- Compares with wiki content to find gaps or outdated info
- Interactively asks user about each update
- Commits and pushes to both repos (respecting DOGMA-PERMISSIONS.md)
Phase 1: Locate Wiki Repository
Step 1.1: Check Argument
The user provided: $ARGUMENTS
If a path or URL was provided:
- If it's a local path: verify it exists and is a git repo
- If it's a GitHub URL: clone it to a temp location or find existing clone
Step 1.2: Search for Existing Wiki Checkout
If no argument provided, search common locations:
# Get current repo name
REPO_NAME=$(basename "$(git rev-parse --show-toplevel)")
# Search parallel directories
ls -d "../${REPO_NAME}.wiki" 2>/dev/null || true
ls -d "../${REPO_NAME}-wiki" 2>/dev/null || true
ls -d "wiki" 2>/dev/null || true
ls -d ".wiki" 2>/dev/null || true
# Search parent directory for any .wiki repos
ls -d ../*.wiki 2>/dev/null || true
Step 1.3: Ask User if Not Found
If wiki repo not found, ask:
Wiki repository not found automatically.
How would you like to provide the wiki location?
1. Enter local path (e.g., ../my-project.wiki)
2. Enter GitHub wiki URL (e.g., https://github.com/user/repo.wiki.git)
3. Skip wiki sync (only update README files in main repo)
4. Cancel
If user provides GitHub URL:
# Clone to parent directory
cd .. && git clone <URL>
Step 1.4: Verify Wiki Repository
Once found/cloned:
SCRIPT_DIR="${CLAUDE_PLUGIN_ROOT:-$(dirname "$(dirname "$(realpath "$0")")")}/scripts"
cd <wiki-path>
git rev-parse --git-dir # Verify it's a git repo
"$SCRIPT_DIR/git-remote-safe.sh" url # Show remote URL (token-safe)
ls -la # List wiki files
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.
- 12d ago First seen · 669 lines · 11 tokens per session scan A 2e156ef89ccc
docs-update is a command published in the GitHub repository Marcel-Bich/marcel-bich-claude-marketplace (13 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 4,528 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-30.
Other commands, from other repositories
migrate
Generate and manage database migrations.
test-suite
Run comprehensive test suite with coverage analysis.
context-stats
Display context window usage and token statistics.
security-scan
Run security audit on codebase.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
run
Execute prompt(s) from ./prompts/ with automatic archiving - for structured prompt-based work.