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/pipelines/code-reviewnpx skills add rios0rios0/pipelines --skill code-reviewgit clone --depth 1 https://github.com/rios0rios0/pipelinesWrote 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/rios0rios0/pipelines/code-review)<a href="https://agentmods.dev/skills/rios0rios0/pipelines/code-review"><img src="https://agentmods.dev/badge/skills/rios0rios0/pipelines/code-review.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00084 | $0.03337 |
| Opus 5 | $0.00042 | $0.01669 |
| Sonnet 5 | $0.00017 | $0.00667 |
| Haiku 4.5 | $0.00008 | $0.00334 |
Grade C, and why
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 5d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- **Downloaded binaries carry a version and a SHA-256** in `global/scripts/shared/pinned-versions.sh` and are fetched through `download_verified` from `verify-download.sh`. **Never `curl | sh`**, and never an unverified Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Downloaded binaries carry a version and a SHA-256** in `global/scripts/shared/pinned-versions.sh` and are fetched through `download_verified` from `verify-download.sh`. **Never `curl | sh`**, and never an unverified Copies of this mod
1 near-identical copy found in the catalogue:
- code-review — 88% identical, 71 lines differ
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code review — pipelines
pipelines provides the reusable workflows, stage templates, shell scripts, and Makefiles that every other repository consumes through make lint, make test, and make sast. A defect here breaks or silently weakens CI everywhere at once, which is why the pinning rules below are absolute.
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 |
Mapper Design Pattern — replacing switch/case |
Mapper-Design-Pattern |
| 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.
- 5d ago First seen · 215 lines · 84 tokens per session scan C 1adbc3ac825f
code-review is a skill published in the GitHub repository rios0rios0/pipelines (22 stars, last pushed 2d ago), licensed MIT. It adds 84 tokens to every session and 3,337 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
CI/CD Pipeline Advanced
Expert-level CI/CD pipeline skill for test automation. Covers GitHub Actions, Jenkins, GitLab CI, Azure DevOps, parallel execution, matrix strategies, caching, artifact management, and deployment gates.
CI/CD Pipeline Config
CI/CD pipeline configuration skill for test automation, covering GitHub Actions, Jenkins, GitLab CI, test parallelization, reporting, and artifact management.
ci-cd-pipeline
Design and implement CI/CD pipelines for automated testing and deployment.
cicd-expert
Expert-level CI/CD with GitHub Actions, Jenkins, deployment pipelines, and automation.
ci-cd-pipeline-generator
Generate production-ready CI/CD pipeline configurations for GitHub Actions, GitLab CI, CircleCI, and Jenkins. Activates when users ask to set up CI/CD, create deployment pipelines, automate build/test/deploy workflows, configure Docker builds, set up staging/production environments, or add quality gates. Covers…
cicd-pipeline-builder
Generate CI/CD pipelines for GitHub Actions, GitLab CI, Jenkins with best practices.