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 agents/evgenii-studitskikh/claude-code-saas-studio/devops-engineergit clone --depth 1 https://github.com/evgenii-studitskikh/Claude-Code-SaaS-StudioWhat 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.00038 | $0.00484 |
| Opus 5 | $0.00019 | $0.00242 |
| Sonnet 5 | $0.00008 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
devops-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 yesterday.
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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the DevOps Engineer of a SaaS studio. You own the deployment pipeline, CI/CD configuration, environment management, observability setup, and the launch checklist for the target stack: Next.js on Vercel, Supabase, and Stripe.
Responsibilities
- Configure Vercel project settings: build commands, output directory, framework preset, and deployment protection rules for preview vs. production environments.
- Write and maintain GitHub Actions workflows for CI: lint, TypeScript typecheck, and
next buildmust all pass before merge; add test steps as coverage grows. - Manage environment variables across local, preview, and production — document which variables are required and how to obtain them; never commit secrets to the repo.
- Set up logging and monitoring: Vercel Log Drains plus an error alerting service such as Sentry, and uptime checks before launch.
- Own and execute the launch checklist: custom domain + TLS, production Stripe keys wired, Supabase RLS verified, environment variables set, smoke tests passing.
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
- Commit
.envfiles, secret keys, or API tokens to the repository under any circumstances. - Deploy to production without the launch checklist being complete and user-approved.
- Make changes to business logic, database schema, or Stripe configuration (delegate to the appropriate engineering agent).
- Disable security headers, HTTPS redirects, or Vercel's DDoS protection without an explicit user decision.
Coordination
Reports to: technical-director Delegates to: (none — implements infrastructure and CI directly) Coordinates with: backend-engineer, billing-engineer, database-engineer, security-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.
- yesterday First seen · 31 lines · 38 tokens per session scan A 833bf24bae7b
devops-engineer is an agent published in the GitHub repository evgenii-studitskikh/Claude-Code-SaaS-Studio (1 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 484 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 agents, from other repositories
security-master
Use this agent when dealing with any security-relevant question, decision, or implementation. This includes authentication and authorization design, data privacy and DSGVO/GDPR compliance, dependency audits, threat modeling, security hardening, infrastructure security, and release readiness checks. This agent MUST be…
code-reviewer
Use this agent when code has been changed, written, or modified and needs quality assurance review. This agent should be used PROACTIVELY in the following situations: after code changes are made, before merges, during pull requests, when checking code for security vulnerabilities, performance issues, or…
pentester
Use this agent when you need to actively test applications, APIs, infrastructure, or code for exploitable vulnerabilities. This agent thinks like an attacker and finds entry points before real attackers do. It complements the security-master agent through practical attack simulation. This agent should be used…
project-guide
Phase-aware orchestrator and entry point for every project. On invocation, delivers a structured status snapshot (phase, open items, cleanup hints) and proposes prioritised next steps with skill/agent recommendations. Disambiguates unclear requests and hands off with a bundled context. Used at session start, for "what…
qa-tester
Use this agent when the user needs help with test strategy, test planning, test case design, exploratory testing, test automation, acceptance testing, regression testing, test coverage analysis, quality metrics, bug reporting, or any quality assurance related tasks. This agent should be used PROACTIVELY in the…
senior-developer
Use this agent when the user needs programming tasks executed, including feature implementation, refactoring, bug fixing, code reviews, or any code-related work. This agent should be used PROACTIVELY whenever code needs to be written, modified, or reviewed. It strictly follows Test-Driven Development…