ODS is a system for turning a PC, Mac, or Linux computer into a private local AI server, meaning a machine that runs models and related AI services itself. It supports local model inference, chat, voice, agents, workflows, document retrieval, search, and image generation. The catalogue includes commands and an instruction for operating or configuring this system.
Borrowing it
Nothing to install: this file belongs to Osmantic/ODS. 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/Osmantic/ODS/main/.claude/commands/docs-update.mdgit clone --depth 1 https://github.com/Osmantic/ODSWrote 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/osmantic/ods/docs-update)<a href="https://agentmods.dev/commands/osmantic/ods/docs-update"><img src="https://agentmods.dev/badge/commands/osmantic/ods/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/osmantic/ods/docs-update"><img src="https://agentmods.dev/badge/commands/osmantic/ods/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.00000 | $0.02760 |
| Opus 5.5 | $0.00000 | $0.01104 |
| Sonnet 5.5 | $0.00000 | $0.00552 |
| Haiku 4.5 | $0.00000 | $0.00276 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ODS Documentation Review and Update
Review all project documentation against recent git changes with full project context. This command understands the installer architecture, extension system, GPU tier mapping, Docker compose layering, dashboard API, and dashboard UI.
Arguments
- commits: Number of recent commits to analyze (default: 20)
- --dry-run: Preview changes without applying them
- --scope: Limit scope to specific docs (default: all)
all- All documentation filesreadme- README.md onlyclaude- CLAUDE.md onlyextensions- Extension-related docs onlydashboard-api- Dashboard API README only
Philosophy: Ask Early, Ask Often
This skill should liberally use AskUserQuestion at decision points. Documentation changes are visible to the whole team and affect onboarding. Confirm scope and validate findings before modifying files.
- Before analyzing — confirm which docs and how many commits to review
- After generating the staleness report — let the user choose which docs to update
- Before applying edits — present proposed changes for approval
- When cross-doc inconsistencies are found — ask which doc is the source of truth
Documentation Files (In-Scope)
| Doc File | Purpose | Scope Key |
|---|---|---|
README.md |
Main project documentation | readme |
CLAUDE.md |
Claude Code instructions | claude |
ods/README.md |
Core product documentation (if exists) | readme |
ods/extensions/services/dashboard-api/README.md |
Dashboard API documentation | dashboard-api |
ods/extensions/services/dashboard/README.md |
Dashboard UI documentation (if exists) | readme |
Excluded Files
node_modules/,.venv/- Dependenciesdata/- Runtime dataods/token-spy/- Dev tools.git/- Git internals
Step 1: Gather Git Context
1.1 Changed Files Analysis
Run git log --oneline -N --name-only --pretty=format: | sort -u | grep -v '^$' (N = commit count, default 20).
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.
- 2mo ago First seen · 337 lines · 0 tokens per session scan A 8deec5b2a496
docs-update is a command published in the GitHub repository Osmantic/ODS (7,712 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,760 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-08-30.
Other commands, from other repositories
review
Review code changes against project conventions.
resume-workflow
Restore the original Moira execution and continue its current step.
save-to-md
Save session documentation with Neo4j memory integration.
revise-claude-md
Update CLAUDE.md with learnings from this session.
check
View the latest screenshot from /Pictures/Screenshots.
deploy
Deploy all MCP plugin servers from .claude-plugin/marketplace.json.