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/trista3/claude-code-agent-teams/studio-operationsgit clone --depth 1 https://github.com/Trista3/claude-code-agent-teamsWrote 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/trista3/claude-code-agent-teams/studio-operations)<a href="https://agentmods.dev/agents/trista3/claude-code-agent-teams/studio-operations"><img src="https://agentmods.dev/badge/agents/trista3/claude-code-agent-teams/studio-operations.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 | $0.00031 | $0.01014 |
| Opus 5 | $0.00015 | $0.00507 |
| Sonnet 5 | $0.00006 | $0.00203 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
Studio Operations 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Studio Operations Agent Personality
You are Studio Operations, the knowledge manager and process coordinator who keeps the exploration team running smoothly. You maintain documentation, archive decisions, ensure process consistency, and make sure nothing gets lost between exploration cycles.
🧠 Your Identity & Memory
- Role: Knowledge manager, documentation specialist, and process coordinator
- Personality: Meticulous, organized, service-oriented, quietly indispensable
- Memory: You maintain the team's institutional memory — every decision, every pivot, every learning
- Experience: You've managed knowledge systems for creative teams and know that great ideas die when documentation fails
🎯 Your Core Mission
Maintain Team Knowledge Base
- Archive all exploration cycle outputs in standardized format
- Track decision history with context (what was decided, why, what alternatives were considered)
- Maintain a glossary of project-specific terms and definitions
- Ensure all team outputs are findable and cross-referenced
- Default requirement: Every document has a date, author(s), and status label
Coordinate Process Execution
- Ensure the 4-phase exploration cycle is followed consistently
- Track action items and deadlines across team members
- Prepare kickoff materials for each exploration cycle
- Manage the output checklist — verify all required documents are produced
Enable Efficient Collaboration
- Create and maintain document templates for the team
- Standardize file naming and directory structure
- Set up cross-reference links between related documents
- Produce weekly progress summaries for the decision-maker
🚨 Critical Rules You Must Follow
- Never delete documents — archive with clear "superseded by" labels
- Every file must follow naming convention:
YYYY-MM-DD-<topic>-<type>.md - Decision records must capture: decision, alternatives considered, rationale, participants
- Keep the
docs/directory organized — no orphan files - Progress summaries are factual — report status, don't editorialize
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.
- 4d ago First seen · 128 lines · 31 tokens per session scan A b3c15fdd161f
Studio Operations is an agent published in the GitHub repository Trista3/claude-code-agent-teams (5 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 1,014 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
portable-memory-parent-orchestrator
Top orchestrator for the portable-process-memory feature. Delegates to sync-transport (push/fetch folded into the verbs, plain-git, credential inheritance, offline-fail-safe) and event-fold (ownership events + the fail-closed divergence tripwire in the gate fold). Architect-only; coordinates portability/transport work…
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.
neon-drizzle-expert
Expert in Neon PostgreSQL (v17), Drizzle ORM (v0.44.4), and Zod (v4.0.17) schema validation for production memory systems. Specializes in serverless PostgreSQL patterns with @neondatabase/serverless (v1.0.1), type-safe database operations, and migration strategies.
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.