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 CoWork-OS/CoWork-OS --skill code-reviewgit clone --depth 1 https://github.com/CoWork-OS/CoWork-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/cowork-os/cowork-os/code-review)<a href="https://agentmods.dev/skills/cowork-os/cowork-os/code-review"><img src="https://agentmods.dev/badge/skills/cowork-os/cowork-os/code-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/cowork-os/cowork-os/code-review"><img src="https://agentmods.dev/badge/skills/cowork-os/cowork-os/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00011 | $0.00318 |
| Opus 5 | $0.00005 | $0.00159 |
| Sonnet 5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
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 10d 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.
What it actually says
Code Review
Purpose
Review code for best practices and potential issues
Routing
- Use when: Use when a user explicitly asks for a code review, bug-risk sweep, or pre-merge feedback for a specific path.
- Do not use when: Don't use when the task is a broad architecture rewrite or only formatting fixes.
- Outputs: Findings grouped by severity and file-level recommendations.
- Success criteria: Returns prioritized issues with concrete fixes and no false-critical claims.
Trigger Examples
Positive
- Use the code-review skill for this request.
- Help me with code review.
- Use when a user explicitly asks for a code review, bug-risk sweep, or pre-merge feedback for a specific path.
- Code Review: provide an actionable result.
Negative
- Don't use when the task is a broad architecture rewrite or only formatting fixes.
- Do not use code-review for unrelated requests.
- This request is outside code review scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| path | string | Yes | Path to the file or folder to review |
Runtime Prompt
- Current runtime prompt length: 320 characters.
- Runtime prompt is defined directly in
../code-review.json.
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.
- 10d ago First seen · 48 lines · 11 tokens per session scan A 65a4c745d0d1
code-review is a skill published in the GitHub repository CoWork-OS/CoWork-OS (449 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 318 once invoked, about $0.0001 per session on Opus 5. 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
diff-review
Render the patch-edit run's accumulated changes as a reviewable diff, surface it through a GenUI choice surface, and persist the user's accept / reject decision into the artifact manifest.
critique-theater
Five-dimension design quality review — score the artifact against craft, brand, accessibility, and copy, then fix what falls short before handing it over.
planning
ONLY for coordinated multi-artifact work: multiple workflows with dependencies, shared data-table schema/migration across tasks, or the user explicitly asked to review a plan first. Load create-tasks via loadtool before calling it (search "create tasks" if not visible). Do NOT use for new one-off workflows…
community-research-insight
Extract structured insight briefs from community research transcripts or notes. Produces pain points, stakeholder needs, opportunity maps, risks, and follow-up questions. Requires human review before publication.
review-preflight
Review tooling for a PR: review-preflight prints REVIEW.md's criteria and the PR's live gate state before a review; ci-triage maps a PR's failing checks to already-filed issues.
github-review
Review a GitHub pull request by collecting GitHub context, applying evidence-backed review rules, and optionally publishing one review.