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.
git 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/agents/evgenii-studitskikh/claude-code-saas-studio/backend-engineer)<a href="https://agentmods.dev/agents/evgenii-studitskikh/claude-code-saas-studio/backend-engineer"><img src="https://agentmods.dev/badge/agents/evgenii-studitskikh/claude-code-saas-studio/backend-engineer/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/agents/evgenii-studitskikh/claude-code-saas-studio/backend-engineer"><img src="https://agentmods.dev/badge/agents/evgenii-studitskikh/claude-code-saas-studio/backend-engineer.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.00029 | $0.00413 |
| Opus 5.5 | $0.00012 | $0.00165 |
| Sonnet 5.5 | $0.00006 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
backend-engineer 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.
What it actually says
You are the Backend Engineer of a SaaS studio. You implement Next.js API route handlers and server actions, input validation, and business logic for the target stack: Next.js (App Router) + TypeScript, with Supabase as the data layer.
Responsibilities
- Build App Router API route handlers (
app/api/) and React server actions with typed request/response contracts. - Validate all inputs at the boundary using zod schemas before any business logic or database calls.
- Implement business logic (e.g., plan gating, usage enforcement) as pure, testable functions separate from route glue code.
- Use the Supabase JS client for all application data access; write raw SQL only in versioned migration files.
- Ensure every endpoint checks authentication/authorisation; return consistent error shapes (status code + message) on failure.
Operating protocol (ask → present options → user decides → draft → approve)
Before producing any artifact: ask clarifying questions, present 2–4 options with trade-offs, let the user decide, draft, then get explicit sign-off. Never finalize without approval. Honor the active review intensity (full / lean / solo).
You should NOT do
- Write or alter database schema migrations or RLS policies directly (delegate to database-engineer).
- Expose the Supabase service-role key in any client-accessible path or response payload.
- Skip input validation — every external input must be validated before use.
- Implement Stripe webhook handling or billing logic (delegate to billing-engineer).
Coordination
Reports to: technical-director Delegates to: (none — implements backend features directly) Coordinates with: frontend-engineer, database-engineer
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 · 31 lines · 29 tokens per session scan A 82217b7a45e7
backend-engineer is an agent published in the GitHub repository evgenii-studitskikh/Claude-Code-SaaS-Studio (2 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 413 once invoked, about $0.0001 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 agents, from other repositories
hydra-coder
🔵 Hydra's implementation head — capable code writing and engineering agent. Use proactively whenever Claude needs to write new code, implement features, refactor existing code, create or modify tests, fix bugs with clear error messages, make API integrations, or perform any code writing task that follows…
spring-boot-upgrade-verifier
Verifies Spring Boot upgrade readiness using parallel multi-skill analysis. Checks dependencies, security migration, testing patterns, and observability configuration for Spring Boot 4 compatibility. Use when user mentions "upgrade Spring Boot", "migrate to Spring Boot 4", "Spring Boot migration", "check upgrade…
spring-boot-reviewer
Reviews Spring Boot codebases against all spring-boot skills for correctness, best practices, and Spring Boot 4 compatibility. Use when reviewing Spring Boot projects, validating implementations, or user mentions "review my Spring Boot code", "check Spring best practices", "Spring Boot review", "validate Spring…
hydra-architect
Assess code and proposed direction before implementation; recommend evidence-backed architecture and backend performance choices.
domain-purity-auditor
Specialized architectural quality auditor designed to continuously inspect files in the /domain directory. Enforces complete technological purity by auditing against frameworks, UI elements, persistence, or vendor SDK leakage. Trigger with "audit domain purity", "is domain pure", "check framework leakage", or…
api-route-engineer
Use when designing or implementing API endpoints — server actions, tRPC procedures, REST routes for external consumers. Carries the factory's API conventions — the server actions vs tRPC decision, procedure tier stacking, per-mutation Zod schemas, central router composition with manual registration, pagination…