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/rios0rios0/guide/code-reviewnpx skills add rios0rios0/guide --skill code-reviewgit clone --depth 1 https://github.com/rios0rios0/guideWhat 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.00071 | $0.02906 |
| Opus 5 | $0.00036 | $0.01453 |
| Sonnet 5 | $0.00014 | $0.00581 |
| Haiku 4.5 | $0.00007 | $0.00291 |
Grade A, and why
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 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.
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.
This is a copy
88% identical to code-review — 65 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.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code review — guide
guide is the canonical standards documentation: it publishes to the GitHub wiki and generates rule files for Claude Code, Cursor, Codex, and GitHub Copilot onto the generated branch. Everything every other repository is reviewed against starts here, so an ambiguous sentence propagates as a misapplied rule everywhere.
When to use this skill
Use it whenever you are asked to review a pull request, a diff, a branch, or staged changes in this repository — and before opening a pull request of your own, as a self-check. It is a review skill: it produces findings, not commits.
Source of truth
The canonical engineering standards live in the rios0rios0/guide wiki. This file is a repo-tailored index into that guide plus the rules that only apply here. Precedence, highest first:
- This repository's
.github/copilot-instructions.md,CLAUDE.md, andCONTRIBUTING.md— they describe this codebase and its load-bearing invariants. - The rios0rios0/guide wiki — the shared standard.
- General language idiom.
When the guide and a general convention disagree, the guide wins. When this file and the guide disagree, the guide wins and this file should be corrected in the same pull request.
Guide pages that apply here
| Topic | Page |
|---|---|
YAML Conventions — .yaml, single quotes, unquoted scalars |
YAML |
| Git Flow — branches, commits, SemVer, breaking changes | Git-Flow |
| Documentation & Change Control — changelog and docs discipline | Documentation-&-Change-Control |
| CHANGELOG Formatting — capitalisation and backticks | CHANGELOG-Formatting |
| Security — OWASP checklist, secret hygiene, SAST | Security |
| CI & CD — pipeline stages and the local quality gates | CI-&-CD |
| Code Style — baseline naming and the operations vocabulary | Code-Style |
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 · 194 lines · 71 tokens per session scan A bb3c8a3e3132
code-review is a skill published in the GitHub repository rios0rios0/guide (2 stars, last pushed 4d ago), licensed MIT. It adds 71 tokens to every session and 2,906 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to code-review, differing in 65 lines, and is treated as a copy.
Other skills, from other repositories
common-exploit-verification
Enforce "No Exploit, No Report" policy with PoC construction standards, false-positive filtering, and evidence collection per vulnerability class across backend, frontend, and mobile. Use when validating security findings, constructing exploit proofs, filtering false positives, or writing pentest findings.
JavaScript Tooling
Development tools, linting, and testing for JavaScript projects.
to-issues
Decompose a PRD and/or SPEC into implementable, vertically-sliced Issues with real blocking edges, then create them in your chosen platform (GitHub or Local). Use after /prd (and optionally /prd-to-spec) to turn requirements into agent-ready tickets. Triggers on: create issues, to-issues, 创建issue, 拆解issue, 生成卡片, 创建卡片…
bug-localization
Identify the precise location of bugs in source code, modules, and systems. Use this skill when debugging applications, investigating test failures, analyzing error reports, tracing runtime issues, or performing root cause analysis. Analyzes stack traces, error messages, failing tests, and code patterns to pinpoint…
code-comment-generator
Generates meaningful comments and documentation for code to improve maintenance and readability. Use when adding documentation to Python or Java code, including function/method docstrings, class documentation, inline explanations for complex logic, and code annotations (TODO, FIXME). Analyzes existing comment style in…
code-smell-detector
Identify and report code smells indicating poor design or maintainability issues in Python code, including duplicate code, magic numbers, hardcoded values, God classes, feature envy, inappropriate intimacy, data clumps, primitive obsession, and long parameter lists. Use when conducting code quality audits, preparing…