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-oxcgit 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-oxc)<a href="https://agentmods.dev/skills/louisbrulenaudet/monorepo-template/review-oxc"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/review-oxc/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-oxc"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/review-oxc.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.00073 | $0.01069 |
| Opus 5 | $0.00036 | $0.00535 |
| Sonnet 5 | $0.00015 | $0.00214 |
| Haiku 4.5 | $0.00007 | $0.00107 |
Grade A, and why
review-oxc 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review OXC
Review the OXC toolchain (oxlint + oxfmt + oxlint-tsgolint) for alignment with current official OXC best practices - linting/formatting quality, speed, and optimal developer experience (DX) and AI collaboration on a modern TypeScript monorepo. Your reply must be a plan of suggested changes: concise, actionable, structured - not only prose.
Invocation
Text after the slash command is additional scope/focus (e.g. "rules only", "formatter") - narrow the review accordingly.
Ground truth (mandatory)
Your pre-trained knowledge of OXC may be outdated (fast-moving project). Do not draft suggestions from memory alone.
- Resolve "OXC" (and "oxfmt" separately if covered) via the Context7 MCP (
resolve-library-id→query-docs): linter config schema, categories/plugins, nested config, formatter options, output formats. - For anything Context7 lacks, use Firecrawl search/scrape restricted to the official domain (
oxc.rs) - linter config reference, output formats (notably the--format=agentcontract), formatter docs, changelog for breaking changes. - Version currency: compare catalog entries (
oxlint,oxfmt,oxlint-tsgolint,oxc-transform-react) in pnpm-workspace.yaml and installed versions against latest stable; flag deprecated rules/config keys still present in config. - Cite the retrieved source next to every finding; label anything unverifiable as Unverified.
Scope artifacts
- .oxlintrc.json, .oxfmtrc.json
- Root scripts in package.json:
lint:check,lint:fix,lint:agent,lint:ci,format:* - .claude/rules/quality/code-style.md ↔
.cursor/rules/quality/code-style.mdc - Hook wiring calling format/lint after edits (
.claude/settings.json,.cursor/hooks.json) - Ignore coverage: which paths oxlint/oxfmt skip vs repo-generated dirs (
dist/,worker-configuration.d.ts)
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 · 63 lines · 73 tokens per session scan A cfe7267962e8
review-oxc is a skill published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 11d ago), licensed Apache-2.0. It adds 73 tokens to every session and 1,069 once invoked, about $0.0004 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.