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/claude-ide-bridge --skill nightly-reviewgit clone --depth 1 https://github.com/Oolab-labs/claude-ide-bridgeWrote 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/claude-ide-bridge/nightly-review)<a href="https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/nightly-review"><img src="https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/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/claude-ide-bridge/nightly-review"><img src="https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/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 | $0.00000 | $0.00274 |
| Sonnet 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 11d 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
1 near-identical copy found in the catalogue:
- nightly-review — 100% identical, 0 lines differ
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.
- 11d ago First seen · 70 lines · 0 tokens per session scan A 091c03000b4b
nightly-review is a skill published in the GitHub repository Oolab-labs/claude-ide-bridge (38 stars, last pushed 4mo 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
docs-decisions
Work on Composio documentation content, Fumadocs configuration, changelogs, docs automation prompts, docs decisions, ADR-style records, and docs review guidance. Use for files under docs/, documentation workflows, or requests to record or update a docs decision. Do not use for SDK runtime changes unless docs are the…
skill-creator
Create new skills (SKILL.md files), modify and improve existing skills, and design skill descriptions for accurate triggering. Use when the user wants to create a new skill from scratch, edit an existing skill, optimize a skill's description, or convert a workflow they just demonstrated into a reusable skill.
sol-luna-router
Route substantial coding or repository-review work through a two-stage Sol commander/verifier and separate Luna Max CLI worker. Use when the user explicitly asks Sol to direct or supervise Luna, explicitly requests this router, needs an isolated auditable Luna-owned implementation with a Sol review loop, or asks to…
idea-team
A structured group discussion for exploring a product idea through three roles: researcher, critic, and analogy finder. The roles look for evidence, weaknesses, and useful comparisons.
codebase-audit
A read-only method for auditing an entire codebase across contracts, data integrity, errors, security, architecture, technical debt, configuration, and caching. It produces prioritized findings and a repair roadmap.
codex-agent
Use when you want a second-opinion review via Codex CLI, cross-verification after another agent implements changes, debugging help, or alternative implementation proposals. Requires Codex CLI to be installed and authenticated.