Borrowing it
Nothing to install: this file belongs to PedroMosquera/squadai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PedroMosquera/squadai/main/.agents/skills/code-review/SKILL.mdgit clone --depth 1 https://github.com/PedroMosquera/squadaiWrote 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/pedromosquera/squadai/code-review)<a href="https://agentmods.dev/skills/pedromosquera/squadai/code-review"><img src="https://agentmods.dev/badge/skills/pedromosquera/squadai/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.
<a href="https://agentmods.dev/skills/pedromosquera/squadai/code-review"><img src="https://agentmods.dev/badge/skills/pedromosquera/squadai/code-review.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00010 | $0.00411 |
| Opus 5.5 | $0.00004 | $0.00164 |
| Sonnet 5.5 | $0.00002 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
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 14d 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.
What it actually says
Code Review Skill
Perform a structured code review of the specified code. Follow this protocol to produce consistent, actionable feedback.
Steps
-
Understand context: Read the code and any related files to understand the purpose and design of the change.
-
Check correctness: Verify that the logic is correct.
- Are all code paths handled?
- Are edge cases covered (null, empty, boundary values)?
- Are error conditions handled properly?
-
Check error handling: Review how errors are managed.
- Are errors propagated with sufficient context?
- Are there silent failures or swallowed exceptions?
- Are retries and timeouts handled where appropriate?
-
Check naming and clarity: Evaluate readability.
- Are variable and function names descriptive?
- Is the code self-documenting or does it need comments?
- Are there magic numbers or unexplained constants?
-
Check test coverage: Assess testing.
- Are new code paths tested?
- Are edge cases and error paths tested?
- Do tests follow the project's testing conventions?
-
Check security: Look for security concerns.
- Are there injection vulnerabilities (SQL, command, template)?
- Are secrets or credentials hardcoded?
- Is user input validated before use?
-
Check performance: Identify performance issues.
- Are there unnecessary allocations or copies?
- Are there N+1 query patterns or redundant I/O?
- Are there unbounded loops or missing pagination?
Output Format
List findings grouped by severity:
Critical
Issues that must be fixed before merging (bugs, security, data loss).
Warning
Issues that should be addressed but are not blocking (style, minor inefficiencies).
Suggestion
Optional improvements (readability, alternative approaches, nice-to-haves).
If no issues are found in a category, omit that section.
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.
- 14d ago Changed · -5 lines · +7 tokens per session f6528d16ed99
- 1mo ago First seen · 64 lines · 3 tokens per session scan A 7b28d2f34962
code-review is a skill published in the GitHub repository PedroMosquera/squadai (10 stars, last pushed 4d ago), licensed MIT. It adds 10 tokens to every session and 411 once invoked, about $0.0000 per session on Opus 5.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
testing-anti-patterns
Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or…
structured-code-review
Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR…
am-agent-security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
quality-gates
Expert knowledge in quality assurance gates, code quality standards, and automated checks. Use when enforcing quality standards.
am-agent-code-refactor
Improve code structure, performance, and maintainability through systematic refactoring. Specializes in legacy modernization and technical debt reduction. Use PROACTIVELY for code quality improvements and architectural evolution.
am-agent-code-standards-enforcer
Enforce coding standards, style guides, and architectural patterns across projects. Specializes in linting configuration, code review automation, and team consistency. Use PROACTIVELY for code quality gates and CI/CD pipeline integration.