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 build-featuregit 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/build-feature)<a href="https://agentmods.dev/skills/evgenii-studitskikh/claude-code-saas-studio/build-feature"><img src="https://agentmods.dev/badge/skills/evgenii-studitskikh/claude-code-saas-studio/build-feature.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.1 | $0.00047 | $0.00615 |
| Opus 5 | $0.00023 | $0.00308 |
| Sonnet 5 | $0.00009 | $0.00123 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
build-feature 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 7d 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.
Implement a complete, shippable vertical slice for exactly one user story: from the UI component through the server action or route handler down to the database query, including error handling and loading states. Non-autonomous: a draft plan is approved before any code is written, and each layer boundary is a checkpoint.
Phases
- Scope the story — read
docs/specs/prd.mdto identify the target user story and its acceptance criteria. If no argument was given, ask the user to specify. Confirm the story is IN_SCOPE (run/scope-checkmentally) and that relevant schema tables exist insupabase/migrations/. If tables are missing, stop and direct to/design-schema. - Draft implementation plan — propose the files that will be created or modified: the Next.js page/component (path under
app/), any shared components undercomponents/, the server action or route handler, and the database query. Show the plan as a file tree with a one-line description for each file. Get approval before writing anything. - Implement UI layer — write the React server and/or client components using shadcn/ui components as defined in
docs/specs/ui.md. Include empty, loading, and error states. Underfullreview, show each component before writing; underlean/solo, write after the plan is approved. - Implement server layer — write the server action (preferred for mutations) or route handler. Validate all inputs with Zod. Enforce tenant scoping by reading the tenant ID from the authenticated session — never accept tenant ID from client input. Handle errors explicitly and return typed results.
- Implement data layer — write the Supabase query using the server-side client (
createServerClientfrom@supabase/ssr). Confirm that RLS policies cover the operation; if a service-role bypass is needed, document why in a code comment and flag for review. - Invoke code review — after all files are written, invoke
/code-reviewautomatically. Do not declare the feature done until the review passes or all findings are acknowledged by the user. Once core features exist, design monetization with/design-pricingthen/setup-billing.
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.
- 7d ago First seen · 23 lines · 47 tokens per session scan A 2b2ed360d089
build-feature is a skill published in the GitHub repository evgenii-studitskikh/Claude-Code-SaaS-Studio (1 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 615 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
fullstack-coding-standards
A reference guide for full-stack development, covering frontend code, APIs, databases, and Java Spring Boot examples. It is intended for explicit use rather than automatic application to every implementation.
frontend-api-integration-patterns
Production-ready patterns for integrating frontend applications with backend APIs, including race condition handling, request cancellation, retry strategies, error normalization, and UI state management.
nextjs-supabase-auth
Expert integration of Supabase Auth with Next.js App Router.
react-nextjs-development
React and Next.js 14+ application development with App Router, Server Components, TypeScript, Tailwind CSS, and modern frontend patterns.
Contract-First Development
How to define, document, and maintain the shared contract between frontend and backend.
Full-Stack Error Handling
Error propagation patterns — backend error shape to API response to frontend fetch wrapper to UI state.