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/fireact-dev/main/fireact-buildernpx skills add fireact-dev/main --skill fireact-buildergit clone --depth 1 https://github.com/fireact-dev/mainWhat 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.00062 | $0.02416 |
| Opus 5 | $0.00031 | $0.01208 |
| Sonnet 5 | $0.00012 | $0.00483 |
| Haiku 4.5 | $0.00006 | $0.00242 |
Grade A, and why
fireact-builder 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 2d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fireact Builder — Post-Installation Customization Skill
You help developers customize and extend their Fireact SaaS apps via natural language. This skill covers adding pages, replacing components, customizing navigation, branding, Cloud Functions, Firestore collections, and i18n.
1. Project Detection
Before doing anything, confirm this is a Fireact project:
- Check
package.jsonfor@fireact.dev/appin dependencies - Check
src/config/app.config.jsonexists - Check
src/App.tsximports from@fireact.dev/app
If any check fails, tell the user this doesn't appear to be a Fireact project and suggest running npx create-fireact-app first.
2. State Reading Protocol
MUST read these files before making any changes to understand the current project state:
| File | What to learn |
|---|---|
src/App.tsx |
Current routing, imports, which components are local vs from @fireact.dev/app |
src/config/app.config.json |
Route paths, permissions, settings |
src/config/stripe.config.json |
Subscription plans |
src/i18n/en.ts |
Existing translation keys |
src/components/ (list files) |
Existing custom components |
functions/src/index.ts |
Existing Cloud Functions |
firestore.rules |
Existing security rules |
3. Customization Playbooks
A. Add New Subscription Page
Use when the user wants a page scoped to a subscription (e.g., "add a reports page", "add an analytics page").
Steps:
-
Create component at
src/components/<PageName>.tsx:- Import
useSubscription,useConfig,useTranslationfrom@fireact.dev/app - Handle loading state (spinner) and error state (redirect to home)
- Use TailwindCSS for styling — no inline styles
- See
references/component-patterns.mdfor template
- Import
-
Add route key to
src/config/app.config.jsonunderpages:"<pageName>": "/subscription/:id/<slug>" -
Add route in
src/App.tsxinside theSubscriptionProvider > SubscriptionLayoutroute block:<Route path={appConfig.pages.<pageName>} element={ <ProtectedSubscriptionRoute requiredPermissions={['access']}> <PageName /> </ProtectedSubscriptionRoute> } />
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 275 lines · 62 tokens per session scan A 4c546d8bff2f
fireact-builder is a skill published in the GitHub repository fireact-dev/main (555 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 2,416 once invoked, about $0.0003 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
planning-with-files-ar
تخطيط مستمر قائم على الملفات لعمل وكلاء الذكاء الاصطناعي متعدد الخطوات. يحتفظ بملفات taskplan.md و findings.md و progress.md على القرص، وتحقن خطافات دورة الحياة سياق التخطيط المحدد للمشروع. تقرأ الاستعادة التلقائية ملفات تخطيط المشروع فقط. يمكن للأمر الصريح session-catchup.py --metadata فحص بيانات وصفية لجلسات الوكيل…
kl-consistency-test
Write, calibrate, and debug the prefill-vs-decode logprob (KL) consistency tests in sglang -- the two independent conditions a zero requires (every operator batch-invariant, and the two paths computing the same function), which helper separates them, how to pick a threshold once they hold, and how to localize a…
i18n-localization
Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
dsh-web-documentation
Use when adding or editing dsh-web README files, docs, AGENTS.md instructions, user-facing configuration text, or bilingual documentation pairs.
baoyu-youtube-transcript
Downloads YouTube video transcripts/subtitles and cover images by URL or video ID. Supports multiple languages, translation, chapters, and speaker identification. Caches raw data for fast re-formatting. Use when user asks to "get YouTube transcript", "download subtitles", "get captions", "YouTube字幕", "YouTube封面"…
indication-dossier
Build a source-backed biomedical indication dossier. Use when a research task asks for disease biology, target rationale, patient segmentation, biomarkers, trials, drugs, competitive landscape, or translational evidence.