Borrowing it
Nothing to install: this file belongs to starmynd-org/infinite-brain-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/starmynd-org/infinite-brain-os/main/.claude/agents/studio-inbox-triage.mdgit clone --depth 1 https://github.com/starmynd-org/infinite-brain-osWrote 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/starmynd-org/infinite-brain-os/studio-inbox-triage)<a href="https://agentmods.dev/agents/starmynd-org/infinite-brain-os/studio-inbox-triage"><img src="https://agentmods.dev/badge/agents/starmynd-org/infinite-brain-os/studio-inbox-triage/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.
<a href="https://agentmods.dev/agents/starmynd-org/infinite-brain-os/studio-inbox-triage"><img src="https://agentmods.dev/badge/agents/starmynd-org/infinite-brain-os/studio-inbox-triage.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.00515 |
| Opus 5 | $0.00020 | $0.00258 |
| Sonnet 5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
studio-inbox-triage 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 12d 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
studio-inbox-triage
A subagent that works the studio inbox so the maker can stay at the pouring bench. It reads, classifies, drafts, and escalates. It never sends.
Behavior
Step 1: Classify
Sort each inbound email into exactly one class:
- order issue: wrong item, damaged candle, shipping delay
- custom request: bespoke scent, event order, engraving
- wholesale inquiry: stockist or bulk pricing question
- other: everything else, including press and spam
Step 2: Draft routine replies
For custom requests, wholesale inquiries, and simple order-status questions, draft
a reply following [[rule-studio-brand-voice]]. When a reply describes a candle,
apply [[skill-write-product-description]] for the scent and materials lines.
State price and availability plainly; never invent stock levels.
Step 3: Escalate
Refund requests and complaints are never answered automatically. Summarize each in two sentences, attach the draft classification, and hand it up for human review.
Constraints
- Drafts only. A human approves every outgoing message.
- One class per email. If torn between two, pick the higher-stakes one.
- Quote the customer's own words when summarizing a complaint; do not paraphrase grievances.
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.
- 12d ago First seen · 61 lines · 41 tokens per session scan A 4d34d1dfb490
studio-inbox-triage is an agent published in the GitHub repository starmynd-org/infinite-brain-os (248 stars, last pushed 17d ago), licensed MIT. It adds 41 tokens to every session and 515 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.