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 initializ/forge --skill code-review-githubgit clone --depth 1 https://github.com/initializ/forgeWrote 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/initializ/forge/code-review-github)<a href="https://agentmods.dev/skills/initializ/forge/code-review-github"><img src="https://agentmods.dev/badge/skills/initializ/forge/code-review-github/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/initializ/forge/code-review-github"><img src="https://agentmods.dev/badge/skills/initializ/forge/code-review-github.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 62 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- low Privilege Escalation · line 54 Skill requests more permissions than appear necessary for its stated functionality. Review if elevated access is justified.Fix: Request only the minimum permissions required. Document why each permission is needed. Remove broad permissions like '*' or 'all'.
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.00030 | $0.01987 |
| Opus 5.5 | $0.00012 | $0.00795 |
| Sonnet 5.5 | $0.00006 | $0.00397 |
| Haiku 4.5 | $0.00003 | $0.00199 |
Grade A, and why
code-review-github 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.
How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review GitHub Integration
Orchestrates GitHub PR workflows for AI code review. Provides tools to list pull requests, post inline review comments, apply labels based on review findings, and (with explicit opt-in) auto-merge clean PRs.
All GitHub API interactions go through the gh CLI. Direct HTTP requests and web searches are denied to ensure all operations are auditable and respect GitHub's rate limiting.
Authentication
export GH_TOKEN="ghp_..."
The token needs read-write access since this skill posts comments, applies labels, and can merge PRs:
| Scope (classic PAT) | Fine-grained permission | Why |
|---|---|---|
repo |
Pull requests: Read & Write | List PRs, post review comments, merge |
repo |
Contents: Read | Read PR diff and file contents |
repo |
Issues: Write | Apply and remove labels |
read:org (optional) |
Organization: Read | Org-level label policies |
Minimum fine-grained token permissions: pull_requests: write, contents: read, issues: write on the target repository.
For read-only review without GitHub interaction, use the code-review skill instead — it only needs read access.
Environment Variables
| Variable | Required | Description |
|---|---|---|
| GH_TOKEN | yes | GitHub personal access token or fine-grained token |
| REVIEW_AUTO_MERGE | no | Set to true to enable guarded auto-merge. Default: disabled |
| REVIEW_LABEL_PREFIX | no | Prefix for review labels (default: review/). Labels: review/approved, review/needs-changes, review/security-concern |
Tool: review_github_list_prs
List open pull requests for a repository, optionally filtered by author or label.
Input:
| Parameter | Type | Required | Description |
|---|---|---|---|
| repo | string | yes | Repository in owner/repo format |
| author | string | no | Filter by PR author username |
| label | string | no | Filter by label |
| limit | integer | no | Maximum PRs to return (default: 10, max: 100) |
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 · 221 lines · 30 tokens per session scan A c754d3c3a7c6
code-review-github is a skill published in the GitHub repository initializ/forge (235 stars, last pushed yesterday), licensed Apache-2.0. It adds 30 tokens to every session and 1,987 once invoked, about $0.0001 per session on Opus 5.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
developer_pr_prep
Prepare branches, diffs, tests, and GitHub PR text from a conversation's code folder.
pr-triage
A pull-request review tool that checks a proposed set of code changes in a Git repository. A pull request is a request to merge one branch of code into another.
pull-request-automation
Audits and improves the pull request workflow for a GitHub repository. Covers PR description templates, auto-labelling, CODEOWNERS, PR size checks, and branch protection rules. Invoked when the user asks to improve the PR process, set up PR automation, or add a PR template.
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
pr-reviewer
A pull-request review workflow for checking team-specific coding style, naming, and code structure. A pull request is a proposed change to a codebase that teammates inspect before merging.
hs-ship
Reconcile an exact reviewed release candidate with live repository policy, then publish or merge only the outward actions the user has authorized. Use when opening or updating a PR, addressing PR review, waiting on required checks, merging, or finishing a landed change. It does not design CI/CD or cloud deployment…