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 reviewgit 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)<a href="https://agentmods.dev/skills/louisbrulenaudet/monorepo-template/review"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/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/louisbrulenaudet/monorepo-template/review"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/review.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.00131 | $0.01572 |
| Opus 5.5 | $0.00052 | $0.00629 |
| Sonnet 5.5 | $0.00026 | $0.00314 |
| Haiku 4.5 | $0.00013 | $0.00157 |
Grade A, and why
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 28d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review
Review the repo, one domain per subagent, and give the owner a verified, prioritized plan with the smallest effective fix per item. A deviation from a checklist is not a finding until it has a repo location, a source, and a concrete consequence.
One domain or ten, the process is the same: one reviewer per domain, in parallel, then one verification pass and one reply. It writes no files.
Registry
Each domains/<id>.md is one domain. Its frontmatter is the registry - id, summary, model, optional applies_when - and its body is what the reviewer follows: ## Ground truth, ## Scope, ## Probe, ## Axes, ## Critical when, ## Overlaps, ## Accepted, optional ## Extra output. The contract every reviewer follows is reviewer.md.
Adding a domain = adding one domains/<id>.md with that frontmatter and those sections. Nothing else lists domains.
Read only the frontmatter here (Glob domains/*.md, first lines of each); each reviewer reads its own domain file in full.
Selector
$ARGUMENTS: the first word is the selector, the rest is the focus.
- none or
all→ every domain. - a domain
id, or ids comma-separated (security,ci) → those. - anything else → print the
id/summarytable and stop.
The focus - a path, a workspace (front-app), diff (files changed against main, uncommitted and untracked included), or free text (caching only) - is passed verbatim to every selected reviewer and narrows each domain's ## Scope.
A domain whose applies_when does not hold is skipped only when selected by all, with one Coverage line not applicable: <reason>; naming it explicitly always runs it.
Execution safety
- No files. No report, scratch, ledger, or notes, in the working tree or elsewhere. Findings live only in the reply.
- Read-only. Source and config are read, never edited. Reviewers run only their domain's
## Probecommands. - Never install, upgrade, run a fixer, deploy, promote, run
preview:*, start a dev server, or call a deployed Worker or Preview unless the user asked. A probe blocked by the sandbox becomes a Needs-validation item naming the restriction; do not work around it. - Implement nothing until the user asks after the reply (Follow-up).
What ships with it
11 files 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.
- 28d ago Changed · -45 lines · +84 tokens per session 0e8c2cc25916
- 1mo ago Changed · -2 lines a1e5f1d51963
- 1mo ago First seen · 127 lines · 47 tokens per session scan A e90c2d6cb43b
review is a skill published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 2d ago), licensed Apache-2.0. It adds 131 tokens to every session and 1,572 once invoked, about $0.0005 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
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.
attach-review-to-pr
Add line-specific review comments to pull requests using GitHub CLI API.
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-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.
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.