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 dublyo/saas-skills --skill saas-kitgit clone --depth 1 https://github.com/dublyo/saas-skillsWrote 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/dublyo/saas-skills/saas-kit)<a href="https://agentmods.dev/skills/dublyo/saas-skills/saas-kit"><img src="https://agentmods.dev/badge/skills/dublyo/saas-skills/saas-kit/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/dublyo/saas-skills/saas-kit"><img src="https://agentmods.dev/badge/skills/dublyo/saas-skills/saas-kit.svg" alt="Reviewed on agentmods" width="80" 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.00140 | $0.01165 |
| Opus 5 | $0.00070 | $0.00583 |
| Sonnet 5 | $0.00028 | $0.00233 |
| Haiku 4.5 | $0.00014 | $0.00117 |
Grade A, and why
saas-kit 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SaaS Kit
Operating Rule
Do not write or edit implementation code until the user has approved a spec.
Use this order:
- Establish or note the SaaS constitution and project rules.
- Clarify the SaaS product with one question at a time.
- Produce a full human-readable SaaS spec.
- Map the spec to Spec Kit/manual artifacts.
- Create or update a plan, checklist, and tasks only after the spec is clear.
- Ask for explicit approval before implementation.
- Only after approval, inspect or modify implementation files.
- Analyze before implementation and converge after implementation.
If the user asks for a review or audit, stay read-only unless they explicitly ask for fixes.
Question Protocol
- Ask at most 10 questions.
- Ask exactly one question per message.
- Each question must have exactly four choices: A, B, C, D.
- Each question must build on the previous answer.
- Recommend one option when helpful, but still present all four.
- Stop early when the product direction is clear enough to write a useful spec.
Prioritize questions in this order:
- Primary SaaS job and target user
- Core workflow and success moment
- Dashboard views and daily user actions
- CRUD objects and ownership rules
- Roles and permissions
- Workflow states and transitions
- Data/provider constraints
- UI density and operational needs
- Testing and verification expectations
- Implementation scope and first release boundary
Planning Bias
Focus on the app's real work, not marketing copy or premature architecture.
Default assumptions:
- Product: core SaaS workflows, dashboards, CRUD, and business functions first.
- Frontend: functional dashboard-first UI, Tailwind CSS by default.
- Backend/data: provider-neutral first; map to PocketBase or Supabase after workflows are clear.
- New app defaults: Next.js, Nuxt.js, or Astro.js for frontend; PocketBase or Supabase for backend/data.
- Existing app: inspect repo conventions after spec approval and follow existing patterns.
What ships with it
10 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.
- agents/openai.yaml 199 B
- references/artifact-lifecycle.md 3.0 KB
- references/constitution-governance.md 3.2 KB
- references/customization-integration.md 3.2 KB
- references/dashboard-crud.md 3.1 KB
- references/implementation-convergence.md 2.9 KB
- references/pocketbase-supabase.md 2.9 KB
- references/spec-kit-lifecycle.md 3.8 KB
- references/testing-verification.md 3.2 KB
- references/workflow-spec.md 2.9 KB
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 · 126 lines · 140 tokens per session scan A 649cc855c163
saas-kit is a skill published in the GitHub repository dublyo/saas-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 140 tokens to every session and 1,165 once invoked, about $0.0007 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.