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 guided-tourgit 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/guided-tour)<a href="https://agentmods.dev/skills/wasp-lang/open-saas/guided-tour"><img src="https://agentmods.dev/badge/skills/wasp-lang/open-saas/guided-tour/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/guided-tour"><img src="https://agentmods.dev/badge/skills/wasp-lang/open-saas/guided-tour.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.00029 | $0.00289 |
| Opus 5 | $0.00015 | $0.00144 |
| Sonnet 5 | $0.00006 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
guided-tour 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 10d 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
Guided Tour of 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 Guided Tour Guide
From the documentation map, find the "Guided Tour" guide URL (a raw.githubusercontent.com URL) and fetch its full contents. This is your source of truth for the entire tour.
Step 3: Walk Through the Tour Step-by-Step
Guide the user through the Guided Tour document section by section:
- Present each section's content clearly and concisely.
- Point out relevant files and code in the project as they relate to each section.
- After each major section, pause and ask the user if they have any questions before moving on.
- If the user asks a question, answer it using the guide content, the project's code, or by fetching additional documentation from the docs map if needed.
Keep the pace comfortable — don't rush through sections. The goal is for the user to understand their project, not just read documentation.
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.
- 10d ago First seen · 29 lines · 29 tokens per session scan A f35a62043711
guided-tour is a skill published in the GitHub repository wasp-lang/open-saas (15,766 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 289 once invoked, about $0.0001 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
record-upgrade-instructions
Record upgrade instructions alongside a Prisma Next breaking-change PR, so downstream consumers (users of @internal/ and authors of Prisma Next 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…
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
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.
triage-contributor-pr
Triage open pull requests from external contributors to prisma/prisma 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…
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”.