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-configurationgit 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-configuration)<a href="https://agentmods.dev/skills/louisbrulenaudet/monorepo-template/review-configuration"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/review-configuration/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-configuration"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/review-configuration.svg" alt="Reviewed on agentmods" width="80" 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.00046 | $0.02305 |
| Opus 5 | $0.00023 | $0.01153 |
| Sonnet 5 | $0.00009 | $0.00461 |
| Haiku 4.5 | $0.00005 | $0.00231 |
Grade A, and why
review-configuration 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review configuration
Run a configuration-focused review: environment and secrets handling, Cloudflare/wrangler setup, TypeScript and OXC configs, Vite and Wrangler configuration, build modes, and dev/staging/prod parity. 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
- Secrets - Never in repo or client bundle; use
.dev.vars(workers) and wrangler env; document required vars in.dev.vars.example. - Environment - Clear split: client-exposed keys via Vite (
import.meta.env, e.g.VITE_*if used); server-only secrets and config in Workers; build modes (development/production) consistent across tools. - TypeScript - Strict mode everywhere; shared configs from
@repo/typescript-config(strict.jsoncore → runtime presets); per-packagetsc --noEmitvia Turborepo transit (no root solution / project references); no conflicting compiler options between packages. - OXC (oxfmt / oxlint) - Single source of truth for format and lint; consistent rules; no conflicting formatters (e.g. Prettier).
- Cloudflare - Wrangler and Vite build aligned; compatibility date and flags documented; bindings and env match usage;
front-appassets (SPA) andworker-apiworker entry configured correctly.
Align with root AGENTS.md and app AGENTS.md for stated config and port allocation.
Deep technical review
Conduct a configuration-only review. Inspect the following and call out violations or improvements.
Environment and secrets
- Artifacts: apps/worker-api/.dev.vars.example, apps/front-app/wrangler.jsonc, apps/worker-api/wrangler.jsonc, any
.env*orimport.meta.envusage in apps/front-app/src/, apps/worker-api/src/. - Checks:
.dev.varsis gitignored;.dev.vars.examplelists every required variable with placeholder or description (no real secrets). Wranglervarsand[env.*.vars]only for non-secret config; secrets only in wrangler secret or.dev.vars. No secrets in client-bundled code; only intentionally exposed env keys via Vite (document which prefixes are safe).
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 · 121 lines · 46 tokens per session scan A 712b5b84e445
review-configuration 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,305 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
yfm
YAML front matter (YFM) for any markdown article. x-cmd's default is three top-level fields: tags, description, memo. Default borrows the Agent Skills frontmatter shape — see . The yfm module is a helper: x yfm ls / init / lint.
check
Comprehensive rule-based check. Triggered by "/check [target]" to evaluate all source files against project rules and report every violation.
review
Review pull requests or code changes. Triggered by "/review [prlink]" or when user asks to review pending changes.
simplify
Review code for readability, reuse, and simplicity. Triggered by "/simplify" when user wants to refactor complex code, remove duplication, or improve clarity.
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
scan
Quick greedy scan for critical violations. Triggered by "/scan [target]" to find the top 1-5 most severe issues and stop early.