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-architecturegit 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-architecture)<a href="https://agentmods.dev/skills/louisbrulenaudet/monorepo-template/review-architecture"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/review-architecture/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-architecture"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/review-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Privilege Escalation · line 47 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- 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.00045 | $0.02244 |
| Opus 5 | $0.00023 | $0.01122 |
| Sonnet 5 | $0.00009 | $0.00449 |
| Haiku 4.5 | $0.00005 | $0.00224 |
Grade A, and why
review-architecture 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 architecture
Run an architecture-focused review of the monorepo: layout, workspace dependencies, Turborepo task graph, app vs package boundaries, dependency direction, and module coupling/cohesion. 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
- Dependency direction - Apps depend on packages; packages must not depend on apps. No circular dependencies between workspaces.
- Single responsibility - Each package has one clear purpose (e.g.
@repo/dtos-common,@repo/enums-common,@repo/typescript-config). - Public API surface - Packages expose a minimal, stable API via barrel exports; internal modules are not re-exported unless intentional.
- Turborepo - Task graph is acyclic; cache boundaries and
dependsOnare correct; no redundant or missing tasks. - Root scripts - Single pnpm entry point for common operations; package scripts + turbo filters for scoped work; port allocation is documented and consistent.
Align with root AGENTS.md and app-level AGENTS.md for stated architecture and naming.
Deep technical review
Conduct an architecture-only review. Inspect the following and call out violations or improvements.
Monorepo layout and boundaries
- Artifacts: pnpm-workspace.yaml, root package.json, apps/ and packages/ directory structure.
- Checks: Workspace globs (
apps/*,packages/*) match actual layout. No app code underpackages/and no shared library code underapps/except app-specific utilities. Clear naming:front-app(React + Vite frontend),worker-api(API worker),dtos-common/enums-common(shared contracts),typescript-config(TS configs only). Optional:worker-frontendas a second Vite app if present.
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 · 45 tokens per session scan A 20b159d4b0d9
review-architecture is a skill published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 11d ago), licensed Apache-2.0. It adds 45 tokens to every session and 2,244 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.