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 commands/taylorbrook/max-msp_cc_framework/max-switchgit clone --depth 1 https://github.com/taylorbrook/MAX-MSP_CC_FrameworkWhat 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.00008 | $0.00299 |
| Opus 5 | $0.00004 | $0.00150 |
| Sonnet 5 | $0.00002 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
max-switch 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 2d 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
/max-switch
Switch the active MAX project to a different existing project.
Behavior
-
If project name provided:
- Validate the project exists under
patches/{name}/ - Call
set_active_project(name, base_dir)to update.active-project.json - Display confirmation with the project's current status summary (stage, progress, last activity)
- Validate the project exists under
-
If no project name provided:
- List all available projects via
list_projects(base_dir) - Display each project with its current stage and last activity
- Ask the user to choose which project to switch to
- List all available projects via
-
Error handling:
- If the named project does not exist, show available projects and suggest correct names
- If no projects exist at all, suggest
/max-newto create one
Skills Referenced
- max-lifecycle -- project switching, project listing, status reading
Python Modules
from src.maxpat.project import set_active_project, list_projects, get_active_project, read_status
Arguments
| Argument | Required | Description |
|---|---|---|
| project-name | No | Name of the project to switch to |
Examples
/max-switch my-synth
/max-switch step-sequencer
/max-switch
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.
- 2d ago First seen · 50 lines · 8 tokens per session scan A e58ce288c203
max-switch is a command published in the GitHub repository taylorbrook/MAX-MSP_CC_Framework (41 stars, last pushed 6d ago), licensed MIT. It adds 8 tokens to every session and 299 once invoked, about $0.0000 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.