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 louisbrulenaudet/monorepo-template --skill review-code-qualitygit clone --depth 1 https://github.com/louisbrulenaudet/monorepo-templateWrote 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/louisbrulenaudet/monorepo-template/review-code-quality)<a href="https://agentmods.dev/skills/louisbrulenaudet/monorepo-template/review-code-quality"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/review-code-quality/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/louisbrulenaudet/monorepo-template/review-code-quality"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/review-code-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 7 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00046 | $0.02364 |
| Opus 5 | $0.00023 | $0.01182 |
| Sonnet 5 | $0.00009 | $0.00473 |
| Haiku 4.5 | $0.00005 | $0.00236 |
Grade A, and why
review-code-quality 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 12d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review code quality
Run a code-quality-focused review: naming conventions, TypeScript strictness, OXC (oxfmt/oxlint) compliance, duplication, readability, error handling patterns, testability, and type safety. Your reply must be a plan of suggested changes: concise, actionable, and structured-not only prose.
Invocation
Text after the slash command is additional scope/focus - narrow the review accordingly. If none given, use the default scope described below.
Best practices alignment
- Naming - Per root AGENTS.md: variables and functions
camelCase; constantsCONSTANT_CASE; constrained string set namesPascalCase, membersCONSTANT_CASEviaas constobjects (notexport enum). No single-letter names except trivial loop indices; descriptive names for exports and public APIs. - TypeScript - Strict mode; no
anyor unsafeaswithout justification; no@ts-ignorewithout comment. Explicit return types on exported functions; inferred where trivial. Zod schemas co-located with inferred types where used. - OXC (oxfmt / oxlint) - Format and lint applied; no disabled rules that hide real issues; consistent style (spaces, double quotes, line width 80).
- Structure - Single responsibility per file/function; files under ~300 lines, functions under ~50 lines where practical; clear separation (DTOs in
@repo/dtos-common, routes, handlers, utils). - Errors - Hono
HTTPExceptionand centralizedonErrorwhere used; avoid leaking internals; safe logging (no sensitive data). - Duplication and dead code - No copy-paste blocks that should be shared; no dead imports or unreachable code; no string literals where shared
as constvalue sets or constants exist.
Align with root and app AGENTS.md for conventions and patterns.
Deep technical review
Conduct a code-quality-only review. Inspect the following and call out violations or improvements.
Naming conventions
- Artifacts: All apps/front-app/src/ and apps/worker-api/src/ (variables, functions, constants, constrained value sets), packages/dtos-common/src/, packages/enums-common/src/.
- Checks: Variables: camelCase (e.g.
blogPostList,postId). Functions: camelCase (e.g.getPost(),validateEmail()). Constants: CONSTANT_CASE (e.g.MAX_RETRIES,DEFAULT_TIMEOUT). Value set object names: PascalCase (e.g.HttpMethod,Status). Members: CONSTANT_CASE (e.g.HttpMethod.GET). Useas constobjects + derived types - neverexport enum. File names: kebab-case for modules; PascalCase for React components infront-app. Exported types: PascalCase.
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.
- 12d ago First seen · 136 lines · 46 tokens per session scan A 7271d8abd1ab
review-code-quality is a skill published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 11d ago), licensed Apache-2.0. It adds 46 tokens to every session and 2,364 once invoked, about $0.0002 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
resolve-fixed-pr-comments
Verify what PR review comments have been addressed (committed/pushed OR uncommitted local changes) and resolve the threads that are genuinely fixed or no longer relevant.
review-local-changes
Review your local uncommitted working-tree changes (git diff plus untracked files) and return actionable improvement suggestions. Use before committing, when nothing has been pushed yet.
review-pr
Review an existing GitHub pull request and post inline review comments on its diff. Use when the changes are on an opened PR rather than your local working tree.
attach-review-to-pr
Add line-specific review comments to pull requests using GitHub CLI API.
critique
Comprehensive multi-perspective review using specialized judges with debate and consensus building.
load-pr-comments
Use to load open/unresolved PR review comments then aggregate them as tasks in .specs/comments/.md for parallel agents to fix.