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/.github/prompts/nightly-code-review.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/nightly-code-review)<a href="https://agentmods.dev/commands/osmantic/ods/nightly-code-review"><img src="https://agentmods.dev/badge/commands/osmantic/ods/nightly-code-review.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.00774 |
| Opus 5 | $0.00000 | $0.00387 |
| Sonnet 5 | $0.00000 | $0.00155 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
nightly-code-review 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 yesterday.
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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nightly Code Review (Autonomous CI Mode)
You are running in a CI pipeline. You MUST operate fully autonomously. Do NOT use AskUserQuestion. Do NOT pause for user input. Do NOT create new files.
Goal
Analyze recent commits and make targeted code improvements. Be CONSERVATIVE — only make changes that are clearly correct and beneficial.
Rules
- NEVER modify protected files:
.github/,.env*,ods/installers/,ods/ods-cli,ods/config/ - ONLY modify
.py,.sh,.ts, and.tsxfiles - Every change must be verifiable as an improvement — do not guess
- Prefer no change over a risky change
- Do NOT add docstrings, comments, or type annotations unless fixing an actual bug requires it
- Do NOT refactor working code for style preferences
- Do NOT add error handling, fallbacks, or defensive checks (project follows Let It Crash principle)
- Do NOT add features or new functionality
- Keep changes minimal and focused — small targeted fixes, not sweeping refactors
Steps
Step 1: Gather Context
Run git log --oneline -N (N = COMMITS_TO_ANALYZE provided below) to see recent changes.
Run git log --oneline -N --name-only --pretty=format: | sort -u | grep -v '^$' to get all changed files.
Step 2: Identify Issues
For each recently changed code file, read it and look for:
- Bugs: Logic errors, off-by-one errors, race conditions, incorrect comparisons
- Dead code: Unused imports, unreachable branches, variables assigned but never read
- Type safety: Missing or incorrect type annotations that could mask bugs
- Simplification: Overly complex logic that can be simplified without changing behavior (KISS principle)
- Ruff violations: Run
ruff check <file>on changed Python files and apply auto-fixes withruff check <file> --fix - ShellCheck violations: Run
shellcheck <file>on changed shell scripts
Step 3: Make Improvements
For each issue found:
- Read the full file to understand context
- Use the Edit tool to make the fix
- Run
python -m py_compile <file>to verify syntax for Python files - Run
bash -n <file>to verify syntax for shell scripts
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.
- yesterday First seen · 77 lines · 0 tokens per session scan A 343027d9216e
nightly-code-review is a command published in the GitHub repository Osmantic/ODS (6,213 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 774 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
gsd:pr-branch
Create a clean PR branch by filtering out .planning/ commits — ready for code review.
review
Review code changes against project conventions.
elegant-code-review
Review the current working diff against the elegant-code decision ladder and propose deletions, honoring the negligence floor.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
fix-comments
Address PR review comments by implementing requested changes automatically.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.