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.
/plugin marketplace add xbim08/awesome-claude-code-pluginsnpx agentmods add plugins/xbim08/awesome-claude-code-plugins/studio-producergit clone --depth 1 https://github.com/xbim08/awesome-claude-code-pluginsWrote 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/plugins/xbim08/awesome-claude-code-plugins/studio-producer)<a href="https://agentmods.dev/plugins/xbim08/awesome-claude-code-plugins/studio-producer"><img src="https://agentmods.dev/badge/plugins/xbim08/awesome-claude-code-plugins/studio-producer.svg" alt="Measured on agentmods" height="20"></a>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 today.
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 — 9 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "studio-producer",
"description": "PROACTIVELY use this agent when coordinating across multiple teams, allocating resources, or optimizing studio workflows. This agent specializes in cross-functional coordination, resource management, and process optimization within the 6-day development cycle. Should be triggered automatically when team dependencies arise, resource conflicts occur, or workflow improvements are needed. Examples:\\n\\n<example>\\nContext: When multiple teams need to collaborate\\nuser: \"We need the design and engineering teams to work together on the new creator dashboard\"\\nassistant: \"Cross-team collaboration requires careful orchestration. Let me use the studio-producer agent to coordinate schedules, define handoffs, and ensure smooth collaboration between design and engineering.\"\\n<commentary>\\nEffective cross-team coordination prevents bottlenecks and ensures aligned delivery.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: During resource allocation discussions\\nuser: \"We have three high-priority features but only two senior engineers available\"\\nassistant: \"Resource constraints require strategic allocation. I'll use the studio-producer agent to analyze team capacity and create an optimal resource plan that balances priorities.\"\\n<commentary>\\nSmart resource allocation maximizes output while preventing team burnout.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: When workflow inefficiencies surface\\nuser: \"The QA process is becoming a bottleneck for releases\"\\nassistant: \"Process bottlenecks kill velocity. Let me use the studio-producer agent to analyze the QA workflow and design improvements that maintain quality while increasing throughput.\"\\n<commentary>\\nContinuous workflow optimization is essential for maintaining rapid development cycles.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Sprint planning and coordination\\nuser: \"We're starting a new 6-day cycle next Monday\"\\nassisWhat 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.
- today First seen · 9 lines scan A 3204432d42af
studio-producer is a plugin published in the GitHub repository xbim08/awesome-claude-code-plugins (10 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.
Other plugins, from other repositories
analyze-issue
Fetches GitHub issue details to create comprehensive implementation specifications, analyzing requirements and planning structured approach with clear implementation steps.
awesome-claude-code-plugins marketplace
Plugin marketplace listing 151 plugins: context-memory, documentation-generator, lyra, analyze-codebase, update-claudemd.
aws-cost-saver
Use this agent to scan AWS accounts for cost optimization opportunities. Features 173 automated checks across 11 domains with AWS Compute Optimizer ML integration, data transfer analysis, and reservation recommendations. Includes Zero Hallucination Pricing System with 21 anti-hallucination rules for accurate savings…
backend-architect
Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n \nContext: Designing a new API\nuser: "We need an API for our social sharing feature.
codebase-documenter
Use this agent when you need to analyze a service or codebase component and create comprehensive documentation in CLAUDE.md files. This agent should be invoked after implementing new services, major refactoring, or when documentation needs updating to reflect the current codebase structure. Examples: Context.
agent-safety-preflight
Claude Code slash command that runs a local AI-agent repo preflight before tool-enabled coding sessions get shell, package-script, MCP, or secret-adjacent scope.