github-code-review

github-code-review is a skill for Claude Code, Codex from StarryCod/cogitum. It costs 18 tokens per session (3,689 once invoked), scanned C, a copy of github-code-review, MIT.

A guide for reviewing code changes and GitHub pull requests. A pull request is a proposed set of changes submitted for discussion before it is merged.

In plain words
What is it for?
Use it to review changes before pushing them or examine open pull requests on GitHub.
Why use it?
It provides a repeatable way to check local work or review submitted changes, including the changed lines and their comments.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to review changes before pushing them or examine open pull requests on GitHub.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/starrycod/cogitum/github-code-review
Install

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.

Any agent
npx skills add StarryCod/cogitum --skill github-code-review
Clone the repo
git clone --depth 1 https://github.com/StarryCod/cogitum

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for github-code-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/starrycod/cogitum/github-code-review/github.svg)](https://agentmods.dev/skills/starrycod/cogitum/github-code-review)
Your own site
<a href="https://agentmods.dev/skills/starrycod/cogitum/github-code-review"><img src="https://agentmods.dev/badge/skills/starrycod/cogitum/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.

agentmods 80×15 button for github-code-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/starrycod/cogitum/github-code-review"><img src="https://agentmods.dev/badge/skills/starrycod/cogitum/github-code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,689 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 88% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.03689
Opus 5.5 $0.00007 $0.01476
Sonnet 5.5 $0.00004 $0.00738
Haiku 4.5 $0.00002 $0.00369

Measured 1mo ago against content hash a75155aebde2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

github-code-review scanned grade C with 2 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.

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

elif grep -q "github.com" ~/.git-credentials 2>/dev/null; then

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

Perform code reviews on local changes before pushing, or review open PRs on GitHub. Most of this skill uses plain `git` — the `gh`/`curl` split only matters for PR-level interactions.
Origin

This is a copy

88% identical to github-code-review — 30 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

cogitum/data/skills/github/github-code-review/SKILL.md · 482 lines

How it starts

The opening of the file, as written. The whole thing — 482 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Code Review

Perform code reviews on local changes before pushing, or review open PRs on GitHub. Most of this skill uses plain git — the gh/curl split only matters for PR-level interactions.

Prerequisites

  • Authenticated with GitHub (see github-auth skill)
  • Inside a git repository

Setup (for PR interactions)

if command -v gh &>/dev/null && gh auth status &>/dev/null; then
  AUTH="gh"
else
  AUTH="git"
  if [ -z "$GITHUB_TOKEN" ]; then
    if [ -f ~/.config/cogitum/.env ] && grep -q "^GITHUB_TOKEN=" ~/.config/cogitum/.env; then
      GITHUB_TOKEN=$(grep "^GITHUB_TOKEN=" ~/.config/cogitum/.env | head -1 | cut -d= -f2 | tr -d '\n\r')
    elif grep -q "github.com" ~/.git-credentials 2>/dev/null; then
      GITHUB_TOKEN=$(grep "github.com" ~/.git-credentials 2>/dev/null | head -1 | sed 's|https://[^:]*:\([^@]*\)@.*|\1|')
    fi
  fi
fi

REMOTE_URL=$(git remote get-url origin)
OWNER_REPO=$(echo "$REMOTE_URL" | sed -E 's|.*github\.com[:/]||; s|\.git$||')
OWNER=$(echo "$OWNER_REPO" | cut -d/ -f1)
REPO=$(echo "$OWNER_REPO" | cut -d/ -f2)

1. Reviewing Local Changes (Pre-Push)

This is pure git — works everywhere, no API needed.

Get the Diff

# Staged changes (what would be committed)
git diff --staged

# All changes vs main (what a PR would contain)
git diff main...HEAD

# File names only
git diff main...HEAD --name-only

# Stat summary (insertions/deletions per file)
git diff main...HEAD --stat

Review Strategy

  1. Get the big picture first:
git diff main...HEAD --stat
git log main..HEAD --oneline
  1. Review file by file — use read_file on changed files for full context, and the diff to see what changed:
git diff main...HEAD -- src/auth/login.py
  1. Check for common issues:
# Debug statements, TODOs, console.logs left behind
git diff main...HEAD | grep -n "print(\|console\.log\|TODO\|FIXME\|HACK\|XXX\|debugger"

# Large files accidentally staged
git diff main...HEAD --stat | sort -t'|' -k2 -rn | head -10

# Secrets or credential patterns
git diff main...HEAD | grep -in "password\|secret\|api_key\|token.*=\|private_key"

# Merge conflict markers
git diff main...HEAD | grep -n "<<<<<<\|>>>>>>\|======="

Read the full file on GitHub · 482 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 1mo ago First seen · 482 lines · 18 tokens per session scan C a75155aebde2

Subscribe to this mod's changes

github-code-review is a skill published in the GitHub repository StarryCod/cogitum (12 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 3,689 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (reaches for credential files, makes network calls). It is 88% identical to github-code-review, differing in 30 lines, and is treated as a copy.

Related

Other skills, from other repositories

hypotheses

Turns a research direction into testable hypotheses with predictions, competing explanations and the experiments that discriminate between them, including the design (controls, randomization, blocking), sample size or seed count, the pre-specified analysis, and the result that would falsify each hypothesis. Use when a…

synthetic-sciences/openscience · 99 tokens

code-review

Review frontend code for best practices, bugs, and improvements. Use when reviewing PRs, checking code quality, or before committing.

echoVic/blade-code · 29 tokens

code-review

Review local code changes. Uses an isolated sub-agent for unbiased analysis when the main agent wrote the code; reviews directly in fresh review-only sessions. Checks correctness, conventions, performance, tests, security, and tech design compliance. Use when the user wants a code review or says "review the diff" /…

open-octo/octo-agent · 83 tokens

pypi-release

This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.

alchemiststudiosDOTai/tunacode · 52 tokens

audit-harness

Use when auditing HARNESS.md, pre-commit hooks, pre-push hooks, architecture gates, or CI workflows for tunacode-cli. This skill treats any mismatch, skipped gate, or failing check as a critical failure and requires manual one-by-one execution rather than make targets, batch wrappers, or summary-only audits.

alchemiststudiosDOTai/tunacode · 69 tokens

install-jazz-github-action

Set up Jazz as a GitHub Action for automated PR code review and on-demand /jazz PR assistance. Use when the user asks to add Jazz to CI, create a GitHub Action workflow, set up PR review automation, enable /jazz commands on PRs, or integrate Jazz with GitHub.

lvndry/jazz · 69 tokens