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 tao12345666333/ankaloop --skill code-reviewgit clone --depth 1 https://github.com/tao12345666333/ankaloopWrote 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/tao12345666333/ankaloop/code-review)<a href="https://agentmods.dev/skills/tao12345666333/ankaloop/code-review"><img src="https://agentmods.dev/badge/skills/tao12345666333/ankaloop/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/tao12345666333/ankaloop/code-review"><img src="https://agentmods.dev/badge/skills/tao12345666333/ankaloop/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.00011 | $0.00203 |
| Opus 5.5 | $0.00004 | $0.00081 |
| Sonnet 5.5 | $0.00002 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00020 |
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 Skill
When reviewing code, follow these best practices:
Review Checklist
- Correctness: Does the code work as intended?
- Readability: Is the code easy to understand?
- Performance: Are there any obvious performance issues?
- Security: Are there any security vulnerabilities?
- Testing: Is the code adequately tested?
- Documentation: Is the code well-documented?
Review Guidelines
- Be constructive and kind
- Focus on the code, not the coder
- Suggest improvements, don't just criticize
- Explain the "why" behind your suggestions
- Prioritize issues by severity
Common Issues to Look For
- Magic numbers and strings
- Duplicated code
- Long functions or methods
- Deep nesting
- Missing error handling
- Hardcoded values
- Poor naming conventions
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 · 33 lines · 11 tokens per session scan A 207ea07fed42
code-review is a skill published in the GitHub repository tao12345666333/ankaloop (55 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 203 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-30.
Other skills, from other repositories
code-refiner
Deep code simplification and refactoring preserving behavior across Python, Go, TypeScript, Rust. Targets complexity, anti-patterns, readability debt. Triggers on: "simplify this code", "refactor for clarity", "reduce complexity", "make this more readable", "tech debt cleanup", "too much nesting". NOT for deepening…
package-evaluator
Use when evaluating an Armory package, auditing agent or hook quality, checking package completion contracts, or reviewing the catalog across package types. Covers single-package and repository-wide audits. Not for LLM prompt optimization or ordinary PR code review.
codebase-advisor
Senior codebase advisor that audits a repository, vets findings, and writes self-contained implementation plans for other agents to execute. Triggers on: "write improvement plans", "create an implementation backlog", "audit and plan fixes", "turn findings into plans", "agent-executable plans", "reconcile plans"…
pr-review
Diff-based PR review across code quality, test coverage, silent failures, type design, and comment quality with severity-ranked findings. Triggers on: "review my PR", "review this code", "check my changes", "audit this PR", "code review". NOT for pre-landing gate, use pre-landing-review.
devils-advocate
Challenges AI-generated plans, code, and designs via pre-mortem, inversion, and Socratic questioning to surface blind spots and failure modes. Triggers on: "challenge this", "devils advocate", "stress test this plan", "poke holes in this", "what am I missing".
package-optimizer
Evaluate one existing package or bounded package family from recorded evaluator evidence and a capability profile, then propose retain, simplify, strengthen, retire, or inconclusive without editing. Use when optimizing a skill, agent, hook, rule, command, utility, or preset; evaluating whether package detail is…