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.
git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflowWrote 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/bybren-llc/safe-agentic-workflow/update-docs)<a href="https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/update-docs"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/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.
<a href="https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/update-docs"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/update-docs.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.00008 | $0.00550 |
| Opus 5.5 | $0.00003 | $0.00220 |
| Sonnet 5.5 | $0.00002 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- update-docs — 100% identical, 0 lines differ
- update-docs — 92% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review current work and identify documentation that needs updating per @CONTRIBUTING.md requirement: "always update docs related to the work we are doing within the PR".
Documentation Assessment
1. Identify Changes
Analyze git diff to understand scope:
git diff origin/dev --name-only
Categorize changes:
- Architecture/workflow changes
- New features or APIs
- Process modifications
- Configuration changes
- Database schema changes
2. Required Documentation Updates
Based on changes, check if these need updates:
High-Level Docs (ALWAYS update in same PR)
- CLAUDE.md: Architecture, commands, setup
- Check if: New commands, workflow changes, tech stack updates
- CONTRIBUTING.md: Development process, workflows
- Check if: Process changes, new requirements, workflow modifications
Specialized Docs
- Database:
docs/database/(schema, RLS, migrations)- Check if: Schema changes, new tables, RLS patterns
- API Docs:
docs/api/(endpoints, webhooks)- Check if: New routes, API changes, webhook modifications
- Feature Docs:
docs/(feature-specific)- Check if: New features, major functionality changes
Code Documentation
- Inline comments: Complex logic
- README: Feature directories
- ADRs:
docs/adr/(architectural decisions)- Check if: Significant architecture decisions made
3. Documentation Checklist
For each doc identified:
- Content accuracy verified
- Examples updated
- Commands/code samples tested
- Links validated
- Markdown linting passed
4. Execute Updates
For each doc needing updates:
- Read current version
- Identify outdated sections
- Update with current information
- Run
yarn lint:md:fix - Add to current commit
Workflow
- Assess changes made in current branch
- Identify all affected documentation
- Present list to user for confirmation
- Execute updates for confirmed docs
- Verify markdown linting passes
- Report completion status
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.
- 1mo ago First seen · 91 lines · 8 tokens per session scan A 1571cd967357
update-docs is a command published in the GitHub repository bybren-llc/safe-agentic-workflow (425 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 550 once invoked, about $0.0000 per session on Opus 5.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
ship
Deploy feature through automated staging validation to production with rollback testing.
clarify
Reduce spec ambiguity via targeted questions with adaptive auto-invocation (planning is 80% of success).
help
Analyze workflow state and provide context-aware guidance with visual progress indicators and recommended next steps.
init
Initialize project documentation, preferences, or design tokens.
help
Category: System Syntax: /help [command|topic].
review-tasks
A command that reviews a task list for fidelity to its source plans, practical executability, dependencies, and ways to verify completion. It can use project requirements, specifications, designs, plans, and repository files.