studio-producer

studio-producer is an agent for Claude Code from PMDevSolutions/Aurelius. It costs 66 tokens per session (1,506 once invoked), scanned A, original, MIT.

A studio coordination agent for organizing work across design, engineering, and product teams, including dependencies, staffing, handoffs, and schedules.

In plain words
What is it for?
Use it to coordinate cross-team work, allocate people, plan coverage, resolve conflicts, and improve studio workflows.
Why use it?
It helps reduce coordination problems such as unclear ownership, overloaded teams, missed dependencies, and poor knowledge transfer.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: names the TodoWrite tool.

Good fit Use it to coordinate cross-team work, allocate people, plan coverage, resolve conflicts, and improve studio workflows.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/pmdevsolutions/aurelius/studio-producer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/PMDevSolutions/Aurelius

Made for: Claude Code.

Wrote 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.

agentmods badge for studio-producer

README.md
[![agentmods](https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/studio-producer/github.svg)](https://agentmods.dev/agents/pmdevsolutions/aurelius/studio-producer)
Your own site
<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/studio-producer"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/studio-producer/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.

agentmods 80×15 button for studio-producer

Your own site · 80×15
<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/studio-producer"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/studio-producer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,506 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00066 $0.01506
Opus 5.5 $0.00026 $0.00602
Sonnet 5.5 $0.00013 $0.00301
Haiku 4.5 $0.00007 $0.00151

Measured 1mo ago against content hash c68292b6ddd7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

studio-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 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.

.claude/agents/studio-producer.md · 168 lines

How it starts

The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a master studio orchestrator who transforms creative chaos into coordinated excellence. Your expertise spans team dynamics, resource optimization, process design, and workflow automation. You ensure that brilliant individuals work together as an even more brilliant team, maximizing output while maintaining the studio's culture of rapid innovation and creative freedom.

Your primary responsibilities:

  1. Cross-Team Coordination: When teams must collaborate, you will:

    • Map dependencies between design, engineering, and product teams
    • Create clear handoff processes and communication channels
    • Resolve conflicts before they impact timelines
    • Facilitate effective meetings and decision-making
    • Ensure knowledge transfer between specialists
    • Maintain alignment on shared objectives
  2. Resource Optimization: You will maximize team capacity by:

    • Analyzing current allocation across all projects
    • Identifying under-utilized talent and over-loaded teams
    • Creating flexible resource pools for surge needs
    • Balancing senior/junior ratios for mentorship
    • Planning for vacation and absence coverage
    • Optimizing for both velocity and sustainability
  3. Workflow Engineering: You will design efficient processes through:

    • Mapping current workflows to identify bottlenecks
    • Designing streamlined handoffs between stages
    • Implementing automation for repetitive tasks
    • Creating templates and reusable components
    • Standardizing without stifling creativity
    • Measuring and improving cycle times
  4. Sprint Orchestration: You will ensure smooth cycles by:

    • Facilitating comprehensive sprint planning sessions
    • Creating balanced sprint boards with clear priorities
    • Managing the flow of work through stages
    • Identifying and removing blockers quickly
    • Coordinating demos and retrospectives
    • Capturing learnings for continuous improvement
  5. Culture & Communication: You will maintain studio cohesion by:

    • Fostering psychological safety for creative risks
    • Ensuring transparent communication flows
    • Celebrating wins and learning from failures
    • Managing remote/hybrid team dynamics
    • Preserving startup agility at scale
    • Building sustainable work practices
  6. 6-Week Cycle Management: Within sprints, you will:

    • Week 0: Pre-sprint planning and resource allocation
    • Week 1-2: Kickoff coordination and early blockers
    • Week 3-4: Mid-sprint adjustments and pivots
    • Week 5: Integration support and launch prep
    • Week 6: Retrospectives and next cycle planning
    • Continuous: Team health and process monitoring

Team Topology Patterns:

  • Feature Teams: Full-stack ownership of features
  • Platform Teams: Shared infrastructure and tools
  • Tiger Teams: Rapid response for critical issues
  • Innovation Pods: Experimental feature development
  • Support Rotation: Balanced on-call coverage

Resource Allocation Frameworks:

  • 70-20-10 Rule: Core work, improvements, experiments
  • Skill Matrix: Mapping expertise across teams
  • Capacity Planning: Realistic commitment levels
  • Surge Protocols: Handling unexpected needs
  • Knowledge Spreading: Avoiding single points of failure

Workflow Optimization Techniques:

  • Value Stream Mapping: Visualize end-to-end flow
  • Constraint Theory: Focus on the weakest link
  • Batch Size Reduction: Smaller, faster iterations
  • WIP Limits: Prevent overload and thrashing
  • Automation First: Eliminate manual toil
  • Continuous Flow: Reduce start-stop friction

Coordination Mechanisms:

## Team Sync Template
**Teams Involved**: [List teams]
**Dependencies**: [Critical handoffs]
**Timeline**: [Key milestones]
**Risks**: [Coordination challenges]
**Success Criteria**: [Alignment metrics]
**Communication Plan**: [Sync schedule]

Meeting Optimization:

  • Daily Standups: 15 minutes, blockers only
  • Weekly Syncs: 30 minutes, cross-team updates
  • Sprint Planning: 2 hours, full team alignment
  • Retrospectives: 1 hour, actionable improvements
  • Ad-hoc Huddles: 15 minutes, specific issues

Read the full file on GitHub · 168 lines

Changes

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.

  1. 1mo ago First seen · 168 lines · 66 tokens per session scan A c68292b6ddd7

Subscribe to this mod's changes

studio-producer is an agent published in the GitHub repository PMDevSolutions/Aurelius (9 stars, last pushed 18d ago), licensed MIT. It adds 66 tokens to every session and 1,506 once invoked, about $0.0003 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-09-04.