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/ahmadulhoq/agentskel/code-reviewernpx skills add ahmadulhoq/agentskel --skill code-reviewergit clone --depth 1 https://github.com/ahmadulhoq/agentskelWrote 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/ahmadulhoq/agentskel/code-reviewer)<a href="https://agentmods.dev/skills/ahmadulhoq/agentskel/code-reviewer"><img src="https://agentmods.dev/badge/skills/ahmadulhoq/agentskel/code-reviewer.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.00024 | $0.00855 |
| Opus 5 | $0.00012 | $0.00428 |
| Sonnet 5 | $0.00005 | $0.00171 |
| Haiku 4.5 | $0.00002 | $0.00085 |
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 3d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer Standards
Review Checklist
- Correctness: Does the code do what it's supposed to?
- Edge cases: Are error conditions handled?
- Style: Does it follow project conventions? Check
.memory/CONVENTIONS.md. - Architecture: Does it comply with the project's architecture standards?
Check .agents/standards/ANDROID_ARCHITECTURE.md. Verify module dependency
rules (:feature → :data OK; no :data↔:data, no :feature↔:feature).
Check UDF in ViewModels. No GlobalBus/FlowBus for cross-module events.
Check .agents/standards/IOS_ARCHITECTURE.md. Verify module boundaries
and dependency direction. Check MVVM/UDF patterns in ViewModels.
Check module dependency rules and layer boundaries. 5. Lint / Static Analysis:
CI runs Detekt on every PR and posts inline comments via Reviewdog. Check that no unresolved Detekt violations exist in new/changed lines.
CI runs SwiftLint. Check that no unresolved violations exist in new/changed lines.
CI runs ESLint/Prettier. Check that no unresolved violations exist in new/changed lines.
If CI runs static analysis, the author must fix violations before approval.
6. Performance: Are there obvious inefficiencies? Consider UX impact.
7. Security: Does it follow security-non-negotiables rules?
8. Tests: Are there adequate tests for the changes?
9. Sacred behaviors: Does this change anything in .memory/SACRED.md?
10. Dependencies:
If the PR touches `libs.versions.toml`, `gradle-wrapper.properties`, or `buildSrc/`,
If the PR touches `Package.swift`, `Podfile`, or `.xcode-version`,
If the PR touches `package.json` or lock files,
verify the correct upgrade tier approval was obtained per
`.agents/standards/DEPENDENCY_MANAGEMENT.md`. Block merge if not.
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.
- 3d ago First seen · 82 lines · 24 tokens per session scan A 81bfc9429b5f
code-reviewer is a skill published in the GitHub repository ahmadulhoq/agentskel (13 stars, last pushed 19d ago), licensed MIT. It adds 24 tokens to every session and 855 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-09-02.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…