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 agentmods add skills/paultyng/skill-issue/review-codenpx skills add paultyng/skill-issue --skill review-codegit clone --depth 1 https://github.com/paultyng/skill-issueWhat 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 | $0.00075 | $0.05201 |
| Opus 5 | $0.00037 | $0.02601 |
| Sonnet 5 | $0.00015 | $0.01040 |
| Haiku 4.5 | $0.00007 | $0.00520 |
Grade B, and why
review-code scanned grade B with 1 finding 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Findings must cite probed evidence (`path:line`, grep output, command result), not pattern-matched suspicion. Per `~/.claude/rules/probe-not-assume.md`. How it starts
The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Structured code review covering architecture, Go best practices, and protobuf/API design. Produces actionable, prioritized findings with code-level references.
Workflow
1. Scope and explore
- Confirm scope with the user: full codebase, specific packages/directories, changed files only (PR or branch diff), or specific concern.
- Resolve scope to a file/package list. Based on what the user requested:
- Changed files (PR or branch): Run
git diff --name-only --diff-filter=d <base>...HEADto get changed files (default<base>ismain). If the user references a PR number, usegh pr diff <number> --name-onlyinstead. Filter to relevant file types (.go,.proto). Derive affected Go packages from the file paths (unique parent directories containing.gofiles). - Explicit paths/packages: The user may specify directories (e.g.
internal/auth/), Go package patterns (e.g../internal/auth/...), or individual files. When given a directory or package pattern, include all files under it. Derive Go package paths for static analysis tool invocations. - Full codebase: No filtering. Explore everything (default).
- Changed files (PR or branch): Run
- Pass the resolved scope (file list and derived package paths) to all exploration and investigation subagents so they only read and analyze scoped files. Static analysis tools receive package paths; manual review subagents receive the file list.
- Explore the scoped code using parallel subagents (
subagent_type="explore"). Read all relevant source files, paying attention to package structure, type definitions, interfaces, import graphs,.gofiles,.protofiles, and test files. - Classify the scope for change-aware subagents:
has_changes: true when scope is "changed files (PR or branch)", or when scope is "explicit paths" and those paths have a diff against the base ref (rungit diff --name-only --diff-filter=d <base>...HEAD -- <paths>to check; default base ismain). False for full-codebase reviews with no diff baseline. When true, derive the changed file list (intersection of scoped files and files with diffs) and carry the base ref forward for subagents that need them.
- Determine which subagents are applicable:
- Architecture and Design: applicable if code files (
.go,.rs,.ts,.tsx,.js,.jsx,.swift,.kt,.kts,.py,.rb) exist in scope - Go Best Practices: applicable if
.gofiles exist in scope - Protobuf and API Design: applicable if
.protofiles exist in scope - Go Static Analysis: applicable if
.gofiles exist in scope - Protobuf Linting: applicable if
.protofiles exist in scope - Regression History: applicable if code files exist in scope and
has_changesis true - Conformance Check: applicable if code files exist in scope (lightweight mode by default; full mode when
conformance_modeisfull) - Dependency Evaluation: applicable if a dependency manifest (
go.mod,package.json,requirements.txt,pyproject.toml,Cargo.toml,Gemfile,mix.exs,composer.json) is in scope andhas_changesis true
- Architecture and Design: applicable if code files (
What ships with it
3 files 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.
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.
- 2d ago First seen · 251 lines · 75 tokens per session scan B 7ee7540588f7
review-code is a skill published in the GitHub repository paultyng/skill-issue (9 stars, last pushed 21d ago), licensed MIT. It adds 75 tokens to every session and 5,201 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
tdd-workflow
Test-driven development workflow.
collection
Choose which SkillNote skill collection is active for this Codex project. Use when the user says "change collection", "switch skills", "use frontend skills", or "show collections".
verify
Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.
expert
Base expert skill.
alpha
Alpha skill.
assistant
Assistant — on any repo, scan README→docs→AGENTS→CONTRIBUTING→PR templates→task runners→devcontainer→CI→configs before code; cite sources; prefer AGENTS.md for agent behavior; portable across Cursor/Copilot/Claude; use agent-toolkit CLI when needed.