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/evgenii-studitskikh/claude-code-saas-studio/setup-stacknpx skills add evgenii-studitskikh/Claude-Code-SaaS-Studio --skill setup-stackgit clone --depth 1 https://github.com/evgenii-studitskikh/Claude-Code-SaaS-StudioWrote 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/evgenii-studitskikh/claude-code-saas-studio/setup-stack)<a href="https://agentmods.dev/skills/evgenii-studitskikh/claude-code-saas-studio/setup-stack"><img src="https://agentmods.dev/badge/skills/evgenii-studitskikh/claude-code-saas-studio/setup-stack.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.00044 | $0.00597 |
| Opus 5 | $0.00022 | $0.00298 |
| Sonnet 5 | $0.00009 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
setup-stack 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.
How it starts
The opening of the file, as written. The whole thing — 23 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap the canonical SaaS Studio stack from scratch: Next.js App Router, TypeScript, Tailwind CSS, shadcn/ui, Supabase client, and Stripe SDK. Non-autonomous: every command and every generated file is shown to the user for approval before execution — nothing runs without sign-off.
Phases
- Confirm prerequisites — check that Node.js >= 18,
npm/pnpm, and the Supabase CLI are available. Report what is found. If the project directory already contains apackage.json, warn the user and ask whether to continue or abort. - Present the scaffold plan — show the exact sequence of commands that will be run:
npx create-next-app@latestwith--typescript --tailwind --app --eslint, followed bynpx shadcn@latest init, thennpm install @supabase/ssr @supabase/supabase-js stripe @stripe/stripe-js. List the commands verbatim. Do not run until the user approves. - Run scaffold — execute the approved commands with
Bash. Stream output; stop and surface any error immediately rather than continuing past a failure. - Write
.env.example— create.env.exampleat the project root with all required keys:NEXT_PUBLIC_SUPABASE_URL,NEXT_PUBLIC_SUPABASE_ANON_KEY,SUPABASE_SERVICE_ROLE_KEY,STRIPE_SECRET_KEY,STRIPE_WEBHOOK_SECRET,NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY,NEXT_PUBLIC_APP_URL. Values must be placeholders (e.g.,your-supabase-url), never real secrets. Show the file contents for approval before writing. - Verify the scaffold — run
tsc --noEmitto confirm TypeScript compiles. Report the result. If it fails, diagnose and propose a fix before proceeding. Honor the review intensity: underfull, walk through each scaffold decision for sign-off; underlean, get a single confirmation before running commands; undersolo, proceed and summarize after. - Next step — point to
/design-architectureor, if the PRD and architecture docs are already approved, to/design-schema.
Output
Project scaffold in the current directory + .env.example. Runs no command and writes no file without explicit approval.
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 · 23 lines · 44 tokens per session scan A 68384dbfe900
setup-stack is a skill published in the GitHub repository evgenii-studitskikh/Claude-Code-SaaS-Studio (1 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 597 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-31.
Other skills, from other repositories
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
create-modal
Create declarative modals using the modal library API. Covers modal types (confirm, input, select, form), sections (Text, Buttons, Input, Textarea, Checkbox, List, Combo, When, Custom), rendering with OverlayModal, and keyboard/mouse handling. Use when adding modals or dialogs to the application.
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
ap-juror
L4 terminal leaf - G7 SIGN-OFF. One independent sign-off panel seat that saw none of the intermediate work. Binary PASS/FAIL on opened evidence; default-FAIL. A FAIL naming a P0/P1 blocker is NOT arbitrable into PASS.
gemigo-cli
Use when the user wants to publish an already-built static website or front-end app through GemiGo, such as a Vite/React/Vue static build, plain HTML/CSS/JS page, landing page, demo, docs site, or small browser app, and get a hosted public URL.
nextclaw-dead-code-governance
当用户要求扫描、识别、清理、常态化治理 NextClaw 仓库里的死代码、无用代码、unused files、unused exports、unused dependencies，尤其是核心包越来越臃肿、想删旧实现或做定期减债时使用。.