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 instructions/arnaldo-delisio/claude-code-studio/agents-mdgit clone --depth 1 https://github.com/arnaldo-delisio/claude-code-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/instructions/arnaldo-delisio/claude-code-studio/agents-md)<a href="https://agentmods.dev/instructions/arnaldo-delisio/claude-code-studio/agents-md"><img src="https://agentmods.dev/badge/instructions/arnaldo-delisio/claude-code-studio/agents-md.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.01644 | $0.01644 |
| Opus 5 | $0.00822 | $0.00822 |
| Sonnet 5 | $0.00329 | $0.00329 |
| Haiku 4.5 | $0.00164 | $0.00164 |
Grade A, and why
claude-code-studio AGENTS.md 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 5d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS - Rapid Selection Guide & Intelligent Orchestrator
Primary Directive: "Agents First, Tools Second - Expert Context Over General Purpose"
⚡ RAPID AGENT SELECTION
🚨 MANDATORY UTILITY AGENTS (5)
NEVER use direct tools for these domains
| Agent | Domain | Trigger Keywords |
|---|---|---|
| file-creator | File/directory creation | "create", "generate", "new file", "setup structure" |
| git-workflow | All git operations | "commit", "branch", "merge", "git", "push", "pull" |
| context-fetcher | Internal documentation | "docs", "README", "internal guide", "project docs" |
| knowledge-fetcher | External research | "search", "Readwise", "Context7", "web search", "find articles" |
| date-checker | Date/time calculations | "when", "schedule", "time since", "date", "timestamp" |
🎯 INSTANT AGENT MATCHING
| User Intent | Primary Agent | Secondary Options |
|---|---|---|
| "Build new feature" | rapid-prototyper | → ui-designer → frontend-developer |
| "Fix this bug" | backend-architect / frontend-developer | + test-writer-fixer (auto-triggers) |
| "Test this code" | test-writer-fixer | + api-tester, performance-benchmarker |
| "Deploy this" | devops-automator | + project-shipper |
| "Design this UI" | ui-designer | → frontend-developer → whimsy-injector |
| "Analyze feedback" | feedback-synthesizer | + ux-researcher |
| "Complex multi-step" | studio-coach | (orchestrates others) |
🔀 COMPLEXITY ROUTING
Simple (1 agent): Direct task → Specialized agent
Medium (2-3 agents): Sequential workflow → Auto-handoffs
Complex (4+ agents): studio-coach → Orchestrated workflow
🎼 ORCHESTRATION WORKFLOWS
🏆 MASTER ORCHESTRATOR: studio-coach
Auto-activates when:
- 4+ agents needed
- Cross-domain complexity
- Multi-phase projects
- Agent coordination required
🎯 AUTO-TRIGGERING AGENTS
| Trigger Event | Agent | Purpose |
|---|---|---|
| Code changes | test-writer-fixer | Immediate test coverage |
| UI/UX changes | whimsy-injector | Add delightful interactions |
| Feature flags mentioned | experiment-tracker | A/B testing setup |
| Complex workflows start | studio-coach | Orchestration management |
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.
- 5d ago First seen · 148 lines · 1,644 tokens per session scan A 79a69b1a1624
claude-code-studio AGENTS.md is an instructions file published in the GitHub repository arnaldo-delisio/claude-code-studio (276 stars, last pushed 1y ago), licensed MIT. It adds 1,644 tokens to every session, about $0.0082 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.