Open SaaS is a starter project for building subscription web applications with React, Node.js, Prisma, and the Wasp full-stack framework. It gives developers common SaaS features such as user accounts, email, background jobs, payments, file uploads, and a landing page. Its catalogue add-ons support AI-assisted development of applications built from the template.
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/wasp-lang/open-saas/getting-startednpx skills add wasp-lang/open-saas --skill getting-startedgit clone --depth 1 https://github.com/wasp-lang/open-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/wasp-lang/open-saas/getting-started)<a href="https://agentmods.dev/skills/wasp-lang/open-saas/getting-started"><img src="https://agentmods.dev/badge/skills/wasp-lang/open-saas/getting-started.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 | $0.00031 | $0.00330 |
| Opus 5 | $0.00015 | $0.00165 |
| Sonnet 5 | $0.00006 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
getting-started 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 5d 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
Getting Started with Open SaaS
Follow these steps in order:
Step 1: Fetch the Documentation Map
Fetch the Open SaaS documentation map from the LLMs.txt index. This contains raw markdown file GitHub URLs of all documentation sections.
Step 2: Fetch the Getting Started Guide
From the documentation map, find the "Getting Started" guide URL (a raw.githubusercontent.com URL) and fetch its full contents. Use this as the source of truth for all instructions below.
Step 3: Check Wasp Installation
Run wasp version to check if Wasp is installed and which version is available.
- If Wasp is installed: Confirm the version to the user and continue to Step 4.
- If Wasp is NOT installed: Walk the user through the installation instructions from the Getting Started guide for their OS (detect the OS from the environment). After installation, verify with
wasp versionbefore continuing.
Step 4: Offer to Help Start the App
Ask the user if they'd like help starting their managed PostgreSQL database and Wasp app according to the instructions in the Getting Started guide.
If yes, walk them through the steps from the guide (starting the database, running migrations, starting the dev server, etc.). If they run into any issues, troubleshoot using the guide's content.
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.
- 5d ago First seen · 31 lines · 31 tokens per session scan A f5c1a8a81828
getting-started is a skill published in the GitHub repository wasp-lang/open-saas (15,713 stars, last pushed 29d ago), licensed MIT. It adds 31 tokens to every session and 330 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
cabloy-spec-generation
This skill should be used for requests to create or maintain a Cabloy repo-specs/ / set, including a PRD, SRS, PDP/WBS, test plan, progress register, suite ADR, or “write the specs”/“plan the suite.” It links product, technical, delivery, acceptance, and decision records after the domain boundary is confirmed. Route…
cabloy-worktree-environment
This skill must be used only when the user explicitly invokes /cabloy-worktree-environment or explicitly asks to perform the named Cabloy worktree-environment setup. It prepares a confirmation-gated, worktree-local Vona and Zova runtime environment for a linked Cabloy Basic or Cabloy Start Git worktree using Git…
cabloy-domain-planning
Use this skill whenever the user wants to plan a new business domain in this Cabloy repo, such as CRM, OA, training, ERP, or a similar long-lived domain. Trigger when the request is about deciding suite-first structure, proposing or validating providerId, suite, and module names, comparing naming options, confirming…
cabloy-contract-loop
Use this skill whenever a Cabloy task crosses the Vona-to-Zova contract boundary: backend DTO, controller, validation, entity, inferred DTO, or OpenAPI changes that should drive SDK, schema, api, model, or rest-output regeneration, or stale generated frontend consumers that may be out of sync with backend truth.…
cabloy-resource-field-update
Use this skill whenever the user wants to update a field on an existing Cabloy backend resource: add a new persisted field, refine validation, add enum-like constraints, attach or change ZovaRender.field / ZovaRender.cell metadata, decide whether vonaModule.fileVersion should change, or demonstrate a custom frontend…
cabloy-spec-execution
Use this skill whenever the user asks to implement, execute, deliver, verify, or close a task from an existing Cabloy suite specification, including requests such as “implement WBS-…”, “execute the approved phase”, “deliver the next spec task”, or “make the repo-specs plan real”. It coordinates one bounded WBS…