Borrowing it
Nothing to install: this file belongs to frostyard/snosi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/frostyard/snosi/main/.github/prompts/update-docs.mdgit clone --depth 1 https://github.com/frostyard/snosiWrote 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/frostyard/snosi/update-docs)<a href="https://agentmods.dev/commands/frostyard/snosi/update-docs"><img src="https://agentmods.dev/badge/commands/frostyard/snosi/update-docs.svg" alt="Measured on agentmods" 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.00000 | $0.00362 |
| Opus 5 | $0.00000 | $0.00181 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
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 today.
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.
What it actually says
Prompt: update documentation after a change
Goal: bring the documentation back in sync with <the change that just landed>.
A task in this repository is not complete until the documentation is reviewed and updated. Work through these, in order:
CLAUDE.md— the operational contract summary an agent reads before any change. Update the section that covers the area you touched. Record why a constraint exists and what breaks without it, not just what the code does.docs/design/(formerlyyeti/) — written for AI consumption: architecture, patterns, and decision rationale rather than user-facing guides. Updatedocs/design/overview.mdplus the focused file for the area (build-pipeline.md,ci-cd.md,sysexts.md,testing.md).- The rest of
docs/— normative contracts and runbooks (see the index indocs/README.md). Change these only when the contract itself changed, and say so explicitly in the pull request. README.md— only when a user-visible output, build target, or supported flow changed.
Guidelines:
- Prefer amending an existing section over appending a new one; duplicated, drifting descriptions of the same mechanism are worse than none.
- Record root causes for bugs that were non-obvious, including the evidence that proved them, so the same investigation is not repeated.
- Mark anything unproven as blocked or provisional. Never describe a gate as passing on the strength of a fixture or static check alone.
- Do not create new planning or note files; add them only when explicitly requested.
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.
- today First seen · 31 lines · 0 tokens per session scan A db964aac2d5f
update-docs is a command published in the GitHub repository frostyard/snosi (24 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 362 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-06.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.