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 aaronnat23/disp8ch --skill github-code-reviewgit clone --depth 1 https://github.com/aaronnat23/disp8chWrote 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/aaronnat23/disp8ch/github-code-review)<a href="https://agentmods.dev/skills/aaronnat23/disp8ch/github-code-review"><img src="https://agentmods.dev/badge/skills/aaronnat23/disp8ch/github-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/aaronnat23/disp8ch/github-code-review"><img src="https://agentmods.dev/badge/skills/aaronnat23/disp8ch/github-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.00000 | $0.00144 |
| Opus 5.5 | $0.00000 | $0.00058 |
| Sonnet 5.5 | $0.00000 | $0.00029 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
github-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 1mo 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
GitHub Code Review
Review code changes with a bias toward concrete bugs, regressions, and missing tests.
Use when
- A pull request or diff needs review before merge.
- A user asks for findings instead of a general summary.
Workflow
- Read the changed files before judging the design.
- Prioritize behavioral regressions, unsafe assumptions, and missing coverage.
- Tie each finding to a file, code path, or concrete scenario.
- Separate must-fix issues from lower-risk polish.
- End with a compact review summary and the tests still needed.
Deliverable
- Ordered findings with concrete evidence.
- Open questions or assumptions.
- Merge-readiness summary.
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.
- 1mo ago First seen · 20 lines · 0 tokens per session scan A d354c2d60646
github-code-review is a skill published in the GitHub repository aaronnat23/disp8ch (100 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 144 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
control-center-review
Review one captured Control Center build before runtime activation.
review-pr
Review GitHub pull requests. Use when user says "review PR", "review pull request", or "/review-pr".
review-this-branch
Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the pass/fail checklist.
workflow-code-review
Run a worker-backed code review using its bundled review lenses: approach correctness, architecture ownership, correctness, guardrails, validation, compatibility, and security. Use when asked to review a PR, branch, diff, or uncommitted changes with workflow-level rigor.
spawn-reviewers
Spawn and collect the reviewer fleet at stage20spawnreviewers. Consumes spawn.json.spec (the authoritative spawn spec from derive-spawn-spec / derive-static-spec), resolves CODEINTELALLOWED and CODEINTELREQUIREROOTARG, builds per-agent prompts from the per-agent template + role suffixes (Bug Hunter A/B, Unified…
present-local
Render the operator-facing local-mode code review results at stage29present. Covers BLOCKING/HIGH/MEDIUM section templates, Justified Findings (PLN-721), Dismissed Findings (PLN-722), Verifier Stats footer (PLN-773), operator-flag descriptions, override precedence rule for stage22b, Validation Summary, and final…