Borrowing it
Nothing to install: this file belongs to pajdarova/FenderStudioProMCP. 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/pajdarova/FenderStudioProMCP/main/CLAUDE.mdgit clone --depth 1 https://github.com/pajdarova/FenderStudioProMCPWrote 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/pajdarova/fenderstudiopromcp/claude-md)<a href="https://agentmods.dev/instructions/pajdarova/fenderstudiopromcp/claude-md"><img src="https://agentmods.dev/badge/instructions/pajdarova/fenderstudiopromcp/claude-md/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/instructions/pajdarova/fenderstudiopromcp/claude-md"><img src="https://agentmods.dev/badge/instructions/pajdarova/fenderstudiopromcp/claude-md.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.04489 | $0.04489 |
| Opus 5 | $0.02244 | $0.02244 |
| Sonnet 5 | $0.00898 | $0.00898 |
| Haiku 4.5 | $0.00449 | $0.00449 |
Grade A, and why
FenderStudioProMCP CLAUDE.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 8d 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Basic commands
Preferences
-
CLAUDE.md, MEMORY.md + memory/ are kept directly in the project folder for portability between machines and are integral part of the repository
-
Files in the repository are in US English even that the conversation is in a different language
Instructions
-
At the start of a session, read this file and MEMORY.md (if it exists). The MEMORY.md should contain an index and short description of files in memory/ directory.
-
At the end of the work, record very important new facts/decisions here and other in memory/. Update the index MEMORY.md.
-
After brainstorming (Claude as sparring partner/advisor/opponent), summarize the key conclusions and decisions into a separate file in memory/ (e.g. memory/brainstorm_.md) — not the full transcript of the discussion, just the substance. Update the index MEMORY.md.
-
Write detailed documentation of code into the source files. If the documentation is missing, add it.
CLAUDE.md — project state
Working notes for Claude Code sessions on this repository. Written 2026-08-07.
This file is a handoff, not documentation. User-facing docs live in WINDOWS.md.
Superseded an earlier undated handoff that existed only in chat, not on disk.
1. What this project is
FenderStudioProMCP, an MCP server that lets an LLM drive a DAW. Originated as
a fork of tiwadara/StudioOneMcp (macOS-only); this project has since added
Windows support, an MCP SDK 2.0 upgrade with dual stdio/HTTP transport, and
Ctrl+K command-palette dispatch, and now lives in its own repository (2026-08-07).
Python package/CLI renamed studio_one_mcp → studio_pro_mcp /
studio-pro-mcp in the same pass (2026-08-07). The MCU MIDI port was later
renamed StudioOneMCP → StudioPro-MCU (2026-08-08) once command-surface
(SURF) CC dispatch was confirmed dead code — see memory/2026-08.md §12.
studio-one-devices/StudioOneMCPPads (the SURF device files) stays
unrenamed; it's unused, not wired to anything. Project state (TASKS.md,
memory/) lives in this repo, not the productivity project anymore — see
memory/2026-08.md §7.
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.
- 8d ago First seen · 312 lines · 4,489 tokens per session scan A d65f12072357
FenderStudioProMCP CLAUDE.md is an instructions file published in the GitHub repository pajdarova/FenderStudioProMCP (0 stars, last pushed 29d ago), licensed MIT. It adds 4,489 tokens to every session, about $0.0224 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 instructions, from other repositories
repobrain copilot-instructions.md
Copilot instructions for study8677/repobrain, covering github copilot bootstrap instructions and hard rule — query the repobrain hub first.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.