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.
git clone --depth 1 https://github.com/Imran-ml/claude-skillsWrote 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/agents/imran-ml/claude-skills/code-reviewer)<a href="https://agentmods.dev/agents/imran-ml/claude-skills/code-reviewer"><img src="https://agentmods.dev/badge/agents/imran-ml/claude-skills/code-reviewer/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/agents/imran-ml/claude-skills/code-reviewer"><img src="https://agentmods.dev/badge/agents/imran-ml/claude-skills/code-reviewer.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.00061 | $0.00539 |
| Opus 5.5 | $0.00024 | $0.00216 |
| Sonnet 5.5 | $0.00012 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
code-reviewer 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 First seen · 78 lines · 61 tokens per session scan A d567d992385d
code-reviewer is an agent published in the GitHub repository Imran-ml/claude-skills (3 stars, last pushed 7mo ago), with no licence file. It adds 61 tokens to every session and 539 once invoked, about $0.0002 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 agents, from other repositories
code-reviewer
General-purpose code reviewer for single files or focused diffs. Use when reviewing specific files or a single diff before merging. Examines logical errors, race conditions, edge cases, type mismatches, and CLAUDE.md compliance. Reports issues by severity with file:line references. For multi-file PR or pre-merge…
migration-reviewer
Database migration safety reviewer. Use before applying any SQL migration (D1, MySQL, PostgreSQL, SQLite), WordPress dbDelta, or ORM migration (Knex, Drizzle, Prisma) to production. Checks for destructive operations, backward compatibility, rollback plans, index coverage, data integrity, ordering, and performance…
api-contract-reviewer
API contract reviewer. Use when changing REST, GraphQL, or RPC endpoints, modifying schemas, or before shipping API changes that downstream consumers depend on. Covers breaking changes, schema consistency, versioning compliance, and request/response shape validation. Read-only. Reports findings by severity with…
cleanup
Finds code that shouldn't exist — dead code, unused exports, orphaned files, stale dependencies, and accumulated cruft. Use for periodic hygiene or before major refactors. For code that exists and runs but is over-built or unnecessarily complex, use simplify instead.
history-reviewer
Git history-aware reviewer. Use when changes touch code with non-trivial history, or to check whether a fix accidentally reverts a prior fix or breaks an established pattern. Uses git blame and log to surface why existing code looks the way it does. Read-only. Reports regressions, reverted fixes, and ignored context…
wp-reviewer
WordPress code reviewer following Human Made and 10up standards. Use when reviewing PHP, hooks, queries, REST endpoints, or block code in a WordPress project — lighter context than the full wp agent. Read-only. Reports correctness, security, and standards-compliance issues by severity with file:line references. For…