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/agentjido/jido_ai/code-reviewnpx 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.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.00015 | $0.00329 |
| Opus 5 | $0.00008 | $0.00164 |
| Sonnet 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 4d 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.
- 4d 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 (203 stars, last pushed 6d ago), licensed Apache-2.0. It adds 15 tokens to every session and 329 once invoked, about $0.0001 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-30.
Other skills, from other repositories
debugging
Guides use of the debugstate tool and runtime introspection to diagnose agent issues between turns. Load this skill when something goes wrong during a session and you need to inspect agent state, token usage, event history, or tool availability.
live-tests
Writes live integration tests that hit the real Copilot API and record responses as replayable fixtures. Use this skill when adding new agent behaviors, provider integrations, or tool interactions that need real-world API coverage.
elixir-cyclic-deps
Detects and removes cyclic compile-time dependencies in Elixir codebases using mix xref, with minimal code changes. Use when the user explicitly asks to check for cycles, remove cyclic dependencies, or fix xref cycle failures. Requires Elixir 1.19 or higher for accurate results.
git
Enforces conventional commit messages and good git hygiene. Use this skill automatically whenever creating commits, preparing PRs, or performing any git operations in this repository.
docs
Maintains evergreen documentation in docs/. Use this skill when a major feature is added, changed, or removed to keep the corresponding explainer up to date. Also use when the user asks to document something or references this skill.
lint-and-format
Runs linting and formatting checks before committing. Use this skill after writing or modifying code to ensure it passes all linters and formatters before creating a commit.