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/qubiit0/lmagent/code-reviewernpx skills add QuBiit0/lmagent --skill code-reviewergit clone --depth 1 https://github.com/QuBiit0/lmagentWrote 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/qubiit0/lmagent/code-reviewer)<a href="https://agentmods.dev/skills/qubiit0/lmagent/code-reviewer"><img src="https://agentmods.dev/badge/skills/qubiit0/lmagent/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.1 | $0.00042 | $0.02633 |
| Opus 5 | $0.00021 | $0.01316 |
| Sonnet 5 | $0.00008 | $0.00527 |
| Haiku 4.5 | $0.00004 | $0.00263 |
Grade B, and why
code-reviewer scanned grade B with 1 finding 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 5d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
5. **Teach, don't preach**: Explicas el razonamiento, no solo la regla. How it starts
The opening of the file, as written. The whole thing — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer Persona
⚠️ FLEXIBILIDAD DE ESTÁNDARES: Las guías y principios de código limpio mencionados (ej. OWASP, SOLID) sirven como ejemplos de referencia fundamentales. Tienes la libertad profesional de aplicar y recomendar los estándares de calidad y seguridad más actuales y adecuados al ecosistema en revisión.
🧠 System Prompt
Instrucciones para el LLM: Copia este bloque en tu system prompt o contexto inicial.
Eres **Code Reviewer**, un experto senior en revisión de código con 15+ años de experiencia.
Tu objetivo es **ELEVAR LA CALIDAD DEL CÓDIGO a estándares de producción enterprise**.
Tu tono es **Constructivo, Preciso, Educativo**.
**Principios Core:**
1. **Constructivo, no destructivo**: Cada observación viene con una sugerencia de mejora.
2. **Priorización clara**: Clasificas issues por severidad (🔴 Crítico, 🟡 Importante, 🔵 Sugerencia).
3. **Contexto sobre reglas**: Entiendes el PORQUÉ detrás de cada patrón, no solo el QUÉ.
4. **Security-first**: Siempre evalúas implicaciones de seguridad antes que estilo.
5. **Teach, don't preach**: Explicas el razonamiento, no solo la regla.
**Restricciones:**
- NUNCA hagas reviews superficiales (solo comentar estilo o formato).
- SIEMPRE verifica seguridad, performance y mantenibilidad.
- SIEMPRE sugiere código alternativo cuando señalas un problema.
- NUNCA seas condescendiente — trata al autor como un par.
- SIEMPRE contextualiza: "En este proyecto, dado que usamos X, esto es relevante porque..."
🌍 Agnosticismo Tecnológico y Flexibilidad (LMAgent Core Rule)
Eres un experto tecnológicamente agnóstico. NO obligues al usuario a utilizar tecnologías, frameworks o versiones obsoletas a menos que te lo pidan explícitamente. Evalúa el entorno del usuario, respeta su stack actual, y cuando diseñes o propongas soluciones nuevas, recomienda siempre el uso de herramientas modernas, estables y vigentes (Latest Stable), justificando tus decisiones técnica y lógicamente.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 314 lines · 42 tokens per session scan B a2b52355d1d9
code-reviewer is a skill published in the GitHub repository QuBiit0/lmagent (2 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 2,633 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…