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 saasroo/build-saas --skill build-web-appgit clone --depth 1 https://github.com/saasroo/build-saasWrote 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/saasroo/build-saas/build-web-app)<a href="https://agentmods.dev/skills/saasroo/build-saas/build-web-app"><img src="https://agentmods.dev/badge/skills/saasroo/build-saas/build-web-app.svg" alt="Measured on agentmods" 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.00062 | $0.02099 |
| Opus 5 | $0.00031 | $0.01050 |
| Sonnet 5 | $0.00012 | $0.00420 |
| Haiku 4.5 | $0.00006 | $0.00210 |
Grade A, and why
build-web-app 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 8d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Web App
This skill guides you through building a complete SaaS web application using the Fireact open-source framework. Fireact provides authentication, subscription management, team collaboration, and Stripe billing out of the box — built on Firebase, React, TypeScript, and TailwindCSS.
When to Use This Skill
- User wants to create a new SaaS web application
- User wants an app with authentication, billing, and team management
- User asks about Fireact or wants to scaffold a Firebase + React + Stripe app
- User wants to add subscription management to a new project
What This Skill Does
- Scaffolds a complete SaaS app using the
create-fireact-appCLI - Configures Firebase (Auth, Firestore, Cloud Functions)
- Sets up Stripe billing with subscription plans
- Enables team management with invitations and permissions
- Customizes branding and UI with TailwindCSS
- Deploys to Firebase Hosting
How to Use
Build me a SaaS app for a project management tool with free and pro plans
Create a web app with Google auth, Stripe billing at $0/$29/$99, and team support
Scaffold a Fireact app for my AI writing tool
Instructions
Step 1: Gather Requirements
Ask the user for the following (provide sensible defaults where possible):
Product name:
What the app does (one-line):
Auth providers needed (email/password, Google, GitHub):
Billing plans:
- Plan name, price, features (for each tier)
Team/multi-user support needed? (yes/no):
Target directory for the project:
If the user provides an app description without answering all questions, infer reasonable defaults:
- Default auth: email/password + Google
- Default plans: Free ($0), Pro ($29/mo), Enterprise ($99/mo)
- Default team support: yes Confirm before proceeding.
Step 2: Prerequisites
Verify the following are installed:
# Node.js v18+
node -v
# Firebase CLI
firebase --version
# Install if missing: npm install -g firebase-tools
# Stripe CLI (for webhook testing)
stripe --version
# Install if missing: brew install stripe/stripe-cli/stripe
What ships with it
7 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.
- 8d ago First seen · 259 lines · 62 tokens per session scan A 2ede0934da24
build-web-app is a skill published in the GitHub repository saasroo/build-saas (6 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 2,099 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-31.
Other skills, from other repositories
sfnext-extensions
Build extensions for Storefront Next using target-config.json, target points, extension routes, and translation namespaces. Use when creating modular features, inserting components into UI targets, adding extension routes, adding a section to an existing page, or using SFDCEXT integration markers. Covers the…
sfnext-page-designer
Integrate Page Designer with Storefront Next using React decorators, component registry, and Region rendering. Use when creating merchant-editable pages, adding Page Designer components with @Component/@AttributeDefinition decorators, using fetchPageFromLoader, or rendering Regions. This is for the React/Storefront…
sfnext-project-setup
Create and configure Storefront Next projects. Use when creating a new storefront, understanding project structure, setting up environment variables, or running the sfnext CLI for the first time. Covers project creation, directory layout, .env configuration, and sfnext CLI basics.
sfnext-routing
Implement file-based routing in Storefront Next with React Router 7. Use when adding new pages, creating layout routes, defining route parameters, or understanding route module exports (loader, action, component, meta). Covers flat-routes conventions, nested layouts, and the app prefix.
sfnext-state-management
Manage client-side state in Storefront Next using React context providers and feature-level Zustand stores. Use when handling basket/auth UI state, creating extension stores (for example store locator), or syncing client-visible state after server mutations. NOT for server-side data loading — see sfnext-data-fetching…
vendure-dashboard-migration
Migrates Vendure Admin UI extensions (legacy Angular-based) to the new React Dashboard.