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 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/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/wasp-lang/open-saas/getting-started"><img src="https://agentmods.dev/badge/skills/wasp-lang/open-saas/getting-started.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00031 | $0.00330 |
| Opus 5.5 | $0.00012 | $0.00132 |
| Sonnet 5.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 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
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.
- 1mo 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 (16,120 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 330 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
record-upgrade-instructions
Record upgrade instructions alongside a Prisma 8 breaking-change PR, so downstream consumers (users of @internal/ and authors of Prisma 8 extensions) can apply the matching code translation automatically via the published upgrade skills. Use when you have refactored framework code and the test suite went red in…
triage-contributor-pr
Triage open pull requests from external contributors to prisma/orm and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.
github-review-iteration
Orchestrates a GitHub PR review loop by delegating triage and implementation to dedicated sub-agents, then repeating until actionable review items are cleared. Use when the user says “address PR review”, “triage review comments”, or “iterate until review is clean”.