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 evgenii-studitskikh/Claude-Code-SaaS-Studio --skill setup-deploygit 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-deploy)<a href="https://agentmods.dev/skills/evgenii-studitskikh/claude-code-saas-studio/setup-deploy"><img src="https://agentmods.dev/badge/skills/evgenii-studitskikh/claude-code-saas-studio/setup-deploy/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/evgenii-studitskikh/claude-code-saas-studio/setup-deploy"><img src="https://agentmods.dev/badge/skills/evgenii-studitskikh/claude-code-saas-studio/setup-deploy.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.00043 | $0.00672 |
| Opus 5.5 | $0.00017 | $0.00269 |
| Sonnet 5.5 | $0.00009 | $0.00134 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
setup-deploy 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.
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.
Configure the project for production deployment on Vercel and add a GitHub Actions CI pipeline that catches regressions before merge. Non-autonomous: the full configuration plan is presented and approved before any files are written or CLI commands are run.
Phases
- Check prerequisites — verify the Vercel CLI is installed (
vercel --version) and the user is logged in (vercel whoami). Check that a GitHub remote exists (git remote -v). Confirm the target Vercel team/org and project name. If any prerequisite is missing, provide the exact setup command and wait for the user to resolve it. - Present the deployment plan — describe what will be done: (a)
vercel linkto create or connect the Vercel project, (b) environment variable wiring fordevelopment,preview, andproductionenvironments using the keys from.env.example, (c) a GitHub Actions workflow file at.github/workflows/ci.ymlwith lint, typecheck, and build jobs. Show the proposed workflow YAML verbatim for approval before writing. - Write the CI workflow — write
.github/workflows/ci.ymlwith three jobs:lint(runseslint),typecheck(runstsc --noEmit), andbuild(runsnext build). Useactions/checkout@v4,actions/setup-node@v4withnode-version-file: .nvmrcorpackage.jsonengines. Cachenode_moduleswithactions/cache. Show the file before writing. - Configure Vercel project — run
vercel link(non-interactive if possible), then walk the user through setting each required environment variable in Vercel for each environment. Provide the exactvercel env addcommands; the user must supply the actual secret values — never prompt the user to paste secrets into the conversation. - Verify CI — present the exact
git commitandgit pushcommands that will be run (including branch name and commit message) and wait for the user's explicit approval before executing either. Only after approval: commit the workflow file, push to a branch, and confirm the GitHub Actions run appears. If it fails, diagnose and propose a fix. Honor the review intensity: underfull, walk through each configuration step for sign-off; underlean, get a single confirmation before running commands; undersolo, proceed and summarize after. - Next step — point to
/launch-checklistas the final gate before going live.
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 · 23 lines · 43 tokens per session scan A 1c9a3113a253
setup-deploy is a skill published in the GitHub repository evgenii-studitskikh/Claude-Code-SaaS-Studio (2 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 672 once invoked, about $0.0002 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-31.
Other skills, from other repositories
factory-deployment
Deployment and infrastructure conventions across builds. Vercel + Neon for web (with PR branch DBs), Cloud Run for Python services (one service per entry-point variant), GitHub Actions matrix-deploy on merge, Terraform with environments/modules layout for AWS / compliance customers, RDS IAM authentication for AWS DBs…
devops
DevOps engineering conventions for team. CI/CD, infra-as-code, observability. Project conventions in .claude/conventions/devops.md override these defaults.
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.