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.
npx skills add Oolab-labs/patchwork-os --skill nightly-reviewgit clone --depth 1 https://github.com/Oolab-labs/patchwork-osWrote 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/skills/oolab-labs/patchwork-os/nightly-review)<a href="https://agentmods.dev/skills/oolab-labs/patchwork-os/nightly-review"><img src="https://agentmods.dev/badge/skills/oolab-labs/patchwork-os/nightly-review/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/skills/oolab-labs/patchwork-os/nightly-review"><img src="https://agentmods.dev/badge/skills/oolab-labs/patchwork-os/nightly-review.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.00548 |
| Opus 5.5 | $0.00000 | $0.00219 |
| Sonnet 5.5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
nightly-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 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.
This is a copy
100% identical to nightly-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Installation
Copy this template to your Claude Desktop scheduled-tasks directory:
mkdir -p ~/.claude/scheduled-tasks/nightly-review
cp /path/to/claude-ide-bridge/templates/scheduled-tasks/nightly-review/SKILL.md \
~/.claude/scheduled-tasks/nightly-review/SKILL.md
Then restart Claude Desktop to detect the new scheduled task. Configure the schedule in Claude Desktop settings under "Scheduled Tasks".
The bridge must be running when this task fires. Start it with
claude-ide-bridge --watchornpm run start-all.
Emergency stop: Set
CLAUDE_CODE_DISABLE_CRON=1in your environment to immediately halt all scheduled cron jobs mid-session. Useful if a task runs amok or you need to suppress scheduled runs temporarily.
name: nightly-review description: Review uncommitted changes, check diagnostics, and summarize test status. Run nightly via Claude Desktop scheduled tasks.
Nightly Code Review
Review the current state of the project and produce a structured report.
Steps
- Call
getGitStatusto check branch state and uncommitted changes - Call
getGitDiffto review the actual changes - Call
getDiagnosticsto check for errors and warnings across the workspace - Call
runTeststo verify the test suite passes
Report Format
# Nightly Review — <date>
## Git
Branch: <name>
Uncommitted: <N files changed, M insertions, K deletions>
## Changes Summary
<file-by-file summary, 1 line per file: what changed and why it looks correct or concerning>
Example: `src/bridge.ts: Added error handling for stale connections (+12 lines)`
## Diagnostics
<N errors, M warnings — list files with errors>
## Tests
<N passed, M failed, K skipped (Xs)>
<list any failures with test name + reason>
## Assessment
<CLEAN | NEEDS ATTENTION | BROKEN>
<1-3 sentences summarizing the overall state and any recommended actions>
Action Matrix
- CLEAN — no action needed
- NEEDS ATTENTION — leave a note for the next session
- BROKEN — flag immediately
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 · 70 lines · 0 tokens per session scan A 091c03000b4b
nightly-review is a skill published in the GitHub repository Oolab-labs/patchwork-os (32 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 548 tokens. A static security scan graded it A with 0 findings. It is 100% identical to nightly-review, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
make-pr-easy-to-review
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".
thermo-nuclear-code-quality-review
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
security-review
Perform a focused security review of pending git changes to identify high-confidence security vulnerabilities with real exploitation potential. Use this skill when the user asks for a security review, security audit, vulnerability scan, or wants to check pending changes on a branch for security issues before merging.…
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
huggingface-llm-trainer
Train or fine-tune language models with TRL or Unsloth on Hugging Face Jobs, including SFT, DPO, GRPO, reward models, and GGUF conversion. Use for cloud LLM training; use huggingface-vision-trainer for vision tasks.