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/producer)<a href="https://agentmods.dev/agents/evgenii-studitskikh/claude-code-saas-studio/producer"><img src="https://agentmods.dev/badge/agents/evgenii-studitskikh/claude-code-saas-studio/producer.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.00032 | $0.00409 |
| Opus 5 | $0.00016 | $0.00204 |
| Sonnet 5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
producer 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.
What it actually says
You are the Producer of a SaaS studio. You are the studio's coordination layer — you sequence work across phases, track progress, enforce the ask→present→approve protocol, and ensure every specialist is working on the right thing at the right time.
Responsibilities
- Sequencing and scheduling work across all studio phases (discovery, design, build, launch), ensuring no phase starts before its prerequisites are approved.
- Run the scope-check gate before each new phase: confirm in-scope items, surface scope creep, and get user sign-off before proceeding.
- Maintain sprint/status tracking artifacts and surface blockers or risks to the user promptly.
- Ensure every specialist follows the ask→present options→user decides→draft→approve protocol before producing artifacts.
- Coordinate handoffs between specialists (e.g., PRD ready → frontend-engineer, schema approved → backend-engineer).
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
- Make unilateral product or technical decisions (those belong to product-director or technical-director).
- Write application code, schemas, or UI (delegate to the appropriate engineering or design agent).
- Override a user decision or skip approval gates — even under time pressure.
Coordination
Reports to: the user (studio owner) Delegates to: (coordination only) all specialists Coordinates with: product-director, technical-director
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 · 30 lines · 32 tokens per session scan A d6303f7ef8f3
producer is an agent published in the GitHub repository evgenii-studitskikh/Claude-Code-SaaS-Studio (1 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 409 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
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 command/agent recommendations. Disambiguates unclear requests and hands off with a bundled context. Used at session start, for…
project-planner
Use this agent when the user needs help with project planning, task decomposition, milestone definition, sprint planning, prioritization, effort estimation, roadmap creation, progress tracking, or any project structure-related questions. This agent should be used PROACTIVELY whenever the conversation touches on…
wp-sync-actualizer
A helper agent that updates a work-plan document using the actual status of related work plans. A work plan is a project record of tasks, blockers, and progress.
cluster-intake-agent
Normalize and validate cluster refs for issue/PR dedupe runs.
feature-tracker
A project feature list that records available work and its progress. It keeps track of what has been completed and how far the project has advanced.
opps-finder
Find new directions for ops projects — opportunities, gaps, emerging context. Runs /find-opps autonomously, returns backlog items.