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 agentmods add skills/react/react/compiler-portnpx skills add react/react --skill compiler-portgit clone --depth 1 https://github.com/react/reactWhat 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 | $0.00035 | $0.01147 |
| Opus 5 | $0.00017 | $0.00574 |
| Sonnet 5 | $0.00007 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00115 |
Grade A, and why
compiler-port 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 yesterday.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Port Compiler Pass
Port a compiler pass from TypeScript to Rust end-to-end.
Arguments:
- $ARGUMENTS: Pass name exactly as it appears in Pipeline.ts log entries (e.g.,
PruneMaybeThrows,SSA,ConstantPropagation)
Step 0: Validate pass name
- Read
compiler/packages/babel-plugin-react-compiler/src/Entrypoint/Pipeline.ts - Search for
name: '$ARGUMENTS'in log entries - If not found, list all available pass names from the
log({...name: '...'})calls and stop - Check the
kindfield of the matching log entry:- If
kind: 'ast', report that test-rust-port only supportshirandreactivekind passes currently and stop - If
kind: 'hir'orkind: 'reactive', proceed
- If
Step 1: Determine TS source files and Rust crate
- Follow the import in Pipeline.ts to find the actual TypeScript file(s) for the pass
- Map the TS folder to a Rust crate using this mapping:
| TypeScript Path | Rust Crate |
|---|---|
src/HIR/ (excluding BuildHIR.ts, HIRBuilder.ts) |
react_compiler_hir |
src/HIR/BuildHIR.ts, src/HIR/HIRBuilder.ts |
react_compiler_lowering |
src/Babel/, src/Entrypoint/ |
react_compiler |
src/CompilerError.ts |
react_compiler_diagnostics |
src/ReactiveScopes/ |
react_compiler_reactive_scopes |
src/<Name>/ |
react_compiler_<name> (1:1, e.g., src/Optimization/ -> react_compiler_optimization) |
- Check if the pass is already ported:
- Check if the corresponding Rust file exists in the target crate
- Check if
compiler/crates/react_compiler/src/entrypoint/pipeline.rsalready calls it - If both are true, report the pass is already ported and stop
Step 2: Gather context
Read the following files (all reads happen in main context):
- Architecture guide:
compiler/docs/rust-port/rust-port-architecture.md - Pass documentation: Check
compiler/packages/babel-plugin-react-compiler/docs/passes/for docs about this pass - TypeScript source: All TypeScript source files for the pass + any helpers imported from the same folder
- Rust pipeline:
compiler/crates/react_compiler/src/entrypoint/pipeline.rs - Rust HIR types: Key type files in
compiler/crates/react_compiler_hir/src/(especiallyhir.rs,environment.rs) - Rust reactive types: For reactive passes, also read
compiler/crates/react_compiler_hir/src/reactive_function.rs - Target crate: If the target crate already exists, read its
Cargo.toml,src/lib.rs, and existing files to understand the current structure
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.
- yesterday First seen · 102 lines · 35 tokens per session scan A 15c953f2bde9
compiler-port is a skill published in the GitHub repository react/react (248,328 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 1,147 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
write-concept
Write or review JavaScript concept documentation pages for the 33 JavaScript Concepts project, following strict structure and quality guidelines.
seo-review
Perform a focused SEO audit on JavaScript concept pages to maximize search visibility, featured snippet optimization, and ranking potential.
fact-check
Verify technical accuracy of JavaScript concept pages by checking code examples, MDN/ECMAScript compliance, and external resources to prevent misinformation.
resource-curator
Find, evaluate, and maintain high-quality external resources for JavaScript concept documentation, including auditing for broken and outdated links.
test-writer
Generate comprehensive Vitest tests for code examples in JavaScript concept documentation pages, following project conventions and referencing source lines.
concept-workflow
End-to-end workflow for creating complete JavaScript concept documentation, orchestrating all skills from research to final review.