oxc-project/oxc is a Rust collection of tools for parsing, transforming, resolving, linting, formatting, and minifying JavaScript and TypeScript. It is used to build and maintain JavaScript development and build toolchains. Catalogue add-ons provide workflows for using Oxc tools.
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 oxc-project/oxc --skill insta-snapshotsgit clone --depth 1 https://github.com/oxc-project/oxcWrote 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/oxc-project/oxc/insta-snapshots)<a href="https://agentmods.dev/skills/oxc-project/oxc/insta-snapshots"><img src="https://agentmods.dev/badge/skills/oxc-project/oxc/insta-snapshots/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/oxc-project/oxc/insta-snapshots"><img src="https://agentmods.dev/badge/skills/oxc-project/oxc/insta-snapshots.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00025 | $0.00275 |
| Opus 5.5 | $0.00010 | $0.00110 |
| Sonnet 5.5 | $0.00005 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
insta-snapshots 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 1mo 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.
What it actually says
Insta snapshots
Run the affected test to generate pending snapshots. Use cargo insta pending-snapshots and read the old .snap and new .snap.new outputs to decide whether each change matches the intended behavior.
Use the CLI instead of the interactive cargo insta review UI or manually editing expected output:
cargo insta pending-snapshots
cargo insta accept --snapshot <snapshot_name>
Scope acceptance to the reviewed snapshots from this task; check cargo insta accept --help if a name or package filter is ambiguous. Avoid workspace-wide acceptance or rejection when unrelated pending snapshots exist. Fix unexpected output in the implementation before accepting it.
After accepting, inspect the snapshot diff and rerun the affected test. Finish with the intended .snap updates and no task-generated .snap.new files left pending. Updating snapshots does not itself call for a commit.
Snapshots record expected output, including successful output in some crates. Linter diagnostic snapshots are under crates/oxc_linter/src/snapshots/; other crates have their own locations. Conformance .snap.md reports use a separate update mechanism; inspect the producing test harness rather than treating them as Insta pending snapshots.
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.
- 1mo ago Changed · -115 lines · +3 tokens per session 0db89b037f8f
- 1mo ago First seen · 137 lines · 22 tokens per session scan A a4867aac228a
insta-snapshots is a skill published in the GitHub repository oxc-project/oxc (23,169 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 275 once invoked, about $0.0001 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
oxc-docs
Comprehensive reference for the JavaScript Oxidation Compiler (Oxc) — a collection of high-performance JavaScript tools written in Rust. Covers parser design (lexer, AST, parser, errors, semantic analysis), architecture (parser, linter, test infrastructure, AST tools), ECMAScript specification and grammar, performance…
handle-regression
Protocol for detecting, isolating, and fixing regressions in test262 pass count. Use when a test run shows fewer passes than expected.
regression-triage
Bulk-classify a list of test262 pass→other transitions from a CI run. Distinct from handle-regression (single fix) and analyze-regression (diff two runs). Use after a merge wave when the sharded run reports N regressions and you need to bucket them by root cause and decide which are false positives.
merge-wave
Triage N open PRs with sharded test262 results, rank by net pass delta, merge winners, close catastrophes. Use when multiple PRs have completed CI and you want to land a batch.
create-issue
Create a new issue file from a test262 failure pattern. Includes smoke test, sample extraction, and proper frontmatter.
test262-pass-rates
Show current test262 pass rates for both the js-host (gc) and standalone targets side by side, from committed baseline summaries — no network fetch, no compile. Use for a quick conformance status check.