Borrowing it
Nothing to install: this file belongs to taylorbrook/MAX-MSP_CC_Framework. 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/taylorbrook/MAX-MSP_CC_Framework/main/.claude/commands/max-onboard.mdgit clone --depth 1 https://github.com/taylorbrook/MAX-MSP_CC_FrameworkWrote 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/commands/taylorbrook/max-msp_cc_framework/max-onboard)<a href="https://agentmods.dev/commands/taylorbrook/max-msp_cc_framework/max-onboard"><img src="https://agentmods.dev/badge/commands/taylorbrook/max-msp_cc_framework/max-onboard/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/commands/taylorbrook/max-msp_cc_framework/max-onboard"><img src="https://agentmods.dev/badge/commands/taylorbrook/max-msp_cc_framework/max-onboard.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.00016 | $0.00523 |
| Opus 5.5 | $0.00006 | $0.00209 |
| Sonnet 5.5 | $0.00003 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
max-onboard 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 2mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/max-onboard
Analyze an existing .maxpat file from any source and produce a structured summary of its contents. This works on any valid .maxpat file -- project patches, downloaded patches, factory examples, or third-party patches.
Behavior
-
Accept path -- the user provides a path to a
.maxpatfile. This can be any file on disk, not limited to project patches. -
Load patch -- read the patch file using read_patch:
patcher, _ = read_patch(path) -
Analyze -- run the full structural analysis:
analysis = patcher.analyze() -
Display analysis -- present the structured Markdown analysis to the user, including:
- Complexity metrics -- object count, connection count, nesting depth
- Object inventory -- objects grouped by domain (MSP, Max, Jitter, MC, Gen, etc.)
- Functional sections -- named groups of related objects (e.g., "Oscillator Section", "Filter Chain")
- Signal chain trees -- audio signal flow from sources to outputs
- Control flow -- notable control origins (loadbang, metro, MIDI inputs) and their targets
- Subpatcher hierarchy -- nested patchers, bpatchers, and poly~ instances
- Parameters -- live.dial, live.slider, param, and other user-controllable parameters
-
Offer next steps -- after displaying the analysis, offer options:
- Create a project from this patch (sets up project directory, copies patch to
generated/) - Start iterating on this patch with
/max-iterate - Just review (no further action)
- Create a project from this patch (sets up project directory, copies patch to
Python Modules
from src.maxpat import read_patch
Arguments
| Argument | Required | Description |
|---|---|---|
| path-to-maxpat | Yes | Path to any .maxpat file (e.g., ~/Downloads/cool-synth.maxpat) |
Examples
/max-onboard ~/Downloads/cool-synth.maxpat
/max-onboard patches/kicksynth/generated/kicksynth.maxpat
/max-onboard "/Applications/Max 9/examples/synths/subtractive.maxpat"
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.
- 2mo ago First seen · 58 lines · 16 tokens per session scan A e32c18b9f662
max-onboard is a command published in the GitHub repository taylorbrook/MAX-MSP_CC_Framework (46 stars, last pushed 4d ago), licensed MIT. It adds 16 tokens to every session and 523 once invoked, about $0.0001 per session on Opus 5.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
sim
Run the EmbodiedGen simulation rendering workflow with sim-cli.
cert-check
Review the current state against certification and platform compliance expectations.
combat-design
Design or revise combat rules, variables, readability, and tuning direction.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
web-build-fix
Diagnose and resolve web build, bundling, or deployment issues.
tech-debt
Track and prioritize technical debt.