Deno is a runtime that executes JavaScript, TypeScript, and WebAssembly programs outside a browser. Developers use it for applications such as web servers, and the catalogue add-ons provide workflows and guidance for Deno projects.
Borrowing it
Nothing to install: this file belongs to denoland/deno. 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/denoland/deno/main/.claude/skills/review-pr/SKILL.mdgit clone --depth 1 https://github.com/denoland/denoWrote 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/denoland/deno/review-pr)<a href="https://agentmods.dev/skills/denoland/deno/review-pr"><img src="https://agentmods.dev/badge/skills/denoland/deno/review-pr.svg" alt="Measured on agentmods" height="20"></a>- Snyk warn
- 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.00039 | $0.01681 |
| Opus 5 | $0.00019 | $0.00840 |
| Sonnet 5 | $0.00008 | $0.00336 |
| Haiku 4.5 | $0.00004 | $0.00168 |
Grade A, and why
review-pr 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 8d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deno PR Reviewer
Review PR $ARGUMENTS on the denoland/deno repository.
Step 1: Gather PR context
Fetch the PR metadata, diff, and comments:
gh pr view $ARGUMENTS --json number,title,body,author,labels,state,reviewDecision,commits,files,isDraft,createdAt,url
gh pr diff $ARGUMENTS
gh pr view $ARGUMENTS --comments --json comments
gh pr checks $ARGUMENTS --json name,state,conclusion 2>/dev/null || echo "No checks found"
Step 2: Gate checks
Before reviewing code, check these gates. If any fail, flag them prominently at the top of your review and do not approve.
- CI status — All checks must pass. Point the author to specific failing
checks. Known flaky tests (labeled
ci-test-flaky) can be re-run. - PR title format — Must follow
type(scope): description. Types:feat,fix,perf,refactor,chore,docs,test,revert,BREAKING. Scope examples:ext/node,ext/fetch,cli,lsp,runtime. - No force pushes — PRs are squash-merged. Authors should push new commits, not rewrite history.
- Focused scope — No drive-by cleanups or unrelated changes. Those belong in separate PRs.
- AI disclosure — If the PR looks AI-generated (boilerplate-heavy, generic comments, suspiciously broad) but has no disclosure, ask about it.
- Linked issue (external contributors) — If the PR author is not a
denolandorg member, the PR must link to an issue. If there is no linked issue, request changes and ask the author to open an issue and discuss the change first.
Step 3: Code review
Read every changed file in the diff. Use the repo tools (Read, Grep, Glob)
to understand surrounding context when needed.
Rust code
- Correctness: Edge cases handled? No
.unwrap()on user-controlled data? - Error handling: Proper error types, meaningful messages, no swallowed errors.
- Performance: No unnecessary allocations/copies, no blocking in async code.
- Safety: No
unsafewithout strong justification. No command injection, path traversal, or permission bypasses. - Permissions: New capabilities must go through Deno's permission system.
Watch
ext/node/especially — Node.js APIs sometimes assume full access. - Dependencies: New Cargo deps need strong justification. Prefer existing deps or stdlib.
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.
- 8d ago First seen · 177 lines · 39 tokens per session scan A 0384a931fff8
review-pr is a skill published in the GitHub repository denoland/deno (108,388 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 1,681 once invoked, about $0.0002 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
tdd-cycle
Red-Green-Refactor TDD loop with mandatory false-positive check.
no-bare-casts
Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
compiler-verify
Use when you need to run all compiler checks (tests, lint, format) before committing. Detects whether TS or Rust code changed and runs the appropriate checks.
code-review
Perform a structured code review of changes, checking for correctness, style, tests, and potential issues.
insta-snapshots
Guide for working with and updating insta snapshot tests in Oxc without terminal interaction.