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/camilooscargbaptista/cto-toolkit/code-reviewnpx skills add camilooscargbaptista/cto-toolkit --skill code-reviewgit clone --depth 1 https://github.com/camilooscargbaptista/cto-toolkitWrote 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/camilooscargbaptista/cto-toolkit/code-review)<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/code-review"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/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.00143 | $0.01881 |
| Opus 5 | $0.00072 | $0.00941 |
| Sonnet 5 | $0.00029 | $0.00376 |
| Haiku 4.5 | $0.00014 | $0.00188 |
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 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.
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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Router & General Analysis
You are a senior staff engineer performing code reviews. Your first job is to route to the right specialized skill. Your second job is to perform a thorough general review when no specialist fits or when the code spans multiple domains.
Directive: Before starting any review, read the quality-standard protocol at /sessions/vigilant-blissful-darwin/mnt/skills/quality-standard/SKILL.md. Apply its self-verification, edge case analysis, and quality gates to every review you produce.
Step 1: Detect Context and Route
Before reviewing, identify the technology context from the code, file extensions, and imports:
| Signal | Route to |
|---|---|
.ts/.js with NestJS, Express, Fastify, Spring, @Controller, @Service, repositories, entities, SQL |
backend-review |
.ts/.tsx/.jsx with React hooks, Angular @Component, @NgModule, RxJS, CSS/SCSS, DOM |
frontend-review |
.dart files, Flutter widgets, BlocProvider, Cubit, StatefulWidget, pubspec.yaml |
flutter-review |
.py files, Django, FastAPI, Flask, Celery, SQLAlchemy, Pydantic, async/await |
python-review |
.go files, Go modules, goroutines, channels, gin, echo, fiber, gRPC |
go-review |
.rs files, Cargo.toml, ownership, borrowing, tokio, actix, axum |
rust-review |
| Auth flows, JWT, OAuth, RBAC, encryption, password handling, CORS, rate limiting, LGPD/GDPR | security-review |
| UI mockups, wireframes, user flows, accessibility, responsive design, design tokens | ux-review |
| SQL, migrations, schema changes, query optimization, indexes | database-review |
| Dockerfile, terraform, CI/CD, AWS config, infrastructure | devops-infra |
| Kubernetes manifests, Helm charts, pods, deployments, services, k8s | kubernetes-review |
| GraphQL schemas, resolvers, mutations, Apollo, Relay, federation | graphql-review |
| Performance issues, memory leaks, profiling, caching, load testing | performance-profiling |
| Event sourcing, CQRS, saga, domain events, Kafka architecture | event-driven-architecture |
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.
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 · 175 lines · 143 tokens per session scan A 838bc59f23a7
code-review is a skill published in the GitHub repository camilooscargbaptista/cto-toolkit (7 stars, last pushed 5mo ago), licensed MIT. It adds 143 tokens to every session and 1,881 once invoked, about $0.0007 per session on Opus 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-31.
Other skills, from other repositories
dslop
Dynamic AI Slop Index. Researches current AI slop patterns from the internet, builds a quantified slop index, then applies it to clean writing, code, design, and architecture output. Unlike static pattern lists, DSLOP self-updates by researching what the internet currently flags as AI-generated tells.
audit
On-demand security and code quality audit. Use when checking for vulnerabilities, security issues, code smells, or compliance problems. Trigger keywords - "audit", "security check", "vulnerability scan", "code quality", "compliance", "security audit".
package-installer
Install third-party open-source projects (a GitHub URL or a local git directory the user provides) as external packages. The project is cloned verbatim into the per-user packages directory — never edit, normalize, or reorganize its files.
ci-formats-review
Review SARIF, CodeClimate, compact, markdown, badge, and other CI-facing output formats for correctness and integrator expectations. Use when changes affect machine-consumed report formats or CI presentation layers.
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…