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 skills add agentjido/jido_ai --skill code-reviewgit clone --depth 1 https://github.com/agentjido/jido_aiWrote 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/agentjido/jido_ai/code-review)<a href="https://agentmods.dev/skills/agentjido/jido_ai/code-review"><img src="https://agentmods.dev/badge/skills/agentjido/jido_ai/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/agentjido/jido_ai/code-review"><img src="https://agentmods.dev/badge/skills/agentjido/jido_ai/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00015 | $0.00332 |
| Opus 5.5 | $0.00006 | $0.00133 |
| Sonnet 5.5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
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 1mo 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
Review code changes, diffs, and modified files for quality and correctness.
When to Use
Activate when users ask to:
- Review code changes or diffs
- Check code quality
- Analyze uncommitted work
- Review changes since diverging from a branch
Workflow
-
Identify Changes
- Use
git_diffto get the current diff - Identify files that have been modified
- Use
-
Analyze Each File
- Read the full file context with
read_file - Understand the purpose of changes
- Check for potential issues
- Read the full file context with
-
Provide Feedback
- Note any bugs or logic errors
- Suggest improvements
- Highlight security concerns
- Comment on code style and conventions
Review Criteria
- Correctness: Does the code do what it's supposed to?
- Security: Are there any vulnerabilities?
- Performance: Are there obvious inefficiencies?
- Maintainability: Is the code readable and well-structured?
- Testing: Are changes adequately tested?
Response Format
Provide structured feedback:
- Summary of changes
- Specific issues found (if any)
- Suggestions for improvement
- Overall assessment
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.
- 1mo ago Changed fea2107f98d5
- 1mo ago First seen · 56 lines · 15 tokens per session scan A b476997da44c
code-review is a skill published in the GitHub repository agentjido/jido_ai (211 stars, last pushed 2d ago), licensed Apache-2.0. It adds 15 tokens to every session and 332 once invoked, about $0.0001 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-30.
Other skills, from other repositories
code-review
Analyze pull requests and diffs for bugs, security vulnerabilities, performance issues, style violations, and test coverage gaps — producing structured, actionable feedback.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
architecture-review
Review a diff or a branch range for the architecture drift lint cannot see. Run the scoped linters and the parity check first. Then work a checklist keyed to dev/docs/ARCHITECTURE.md: new Api operations or contract shapes without a ruling, new or cut edges between modules, authorization or audit hand-rolled beside the…
prs-awaiting-maintainer
List open pull requests where the ball is in the maintainer's court: CI is green and the PR is ready for a maintainer to review, re-review, or merge. Use when the user wants to see PRs awaiting maintainer action.
compliance-checker
Check affiliate content for FTC compliance and platform rules. Triggers on: "check my content for compliance", "FTC disclosure check", "is this legal", "review for compliance", "check affiliate disclosure", "am I FTC compliant", "audit my content", "compliance review", "legal check", "platform rules check", "check…
review-pr
Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "the review-pr skill".