MAX-MSP_CC_Framework: Command for Claude Code

.claude/commands/max-test.md

max-test is a command for Claude Code from taylorbrook/MAX-MSP_CC_Framework. It costs 11 tokens per session (1,050 once invoked), scanned A, original, MIT.

A command that creates a manual test checklist for MAX patches, which are projects made in the MAX visual programming environment.

In plain words
What is it for?
Use it to test whether patches load correctly, pass audio signals, respond to MIDI notes, and handle user interactions as expected.
Why use it?
It turns the patch's detected audio, MIDI, and interface elements into concrete checks before you rely on the result.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths.

This is taylorbrook/MAX-MSP_CC_Framework's own configuration. It tells Claude Code how to work on MAX-MSP_CC_Framework itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything MAX-MSP_CC_Framework configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/taylorbrook/MAX-MSP_CC_Framework/main/.claude/commands/max-test.md
Clone the repo
git clone --depth 1 https://github.com/taylorbrook/MAX-MSP_CC_Framework

Made for: Claude Code.

Wrote 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.

agentmods badge for max-test

README.md
[![agentmods](https://agentmods.dev/badge/commands/taylorbrook/max-msp_cc_framework/max-test/github.svg)](https://agentmods.dev/commands/taylorbrook/max-msp_cc_framework/max-test)
Your own site
<a href="https://agentmods.dev/commands/taylorbrook/max-msp_cc_framework/max-test"><img src="https://agentmods.dev/badge/commands/taylorbrook/max-msp_cc_framework/max-test/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.

agentmods 80×15 button for max-test

Your own site · 80×15
<a href="https://agentmods.dev/commands/taylorbrook/max-msp_cc_framework/max-test"><img src="https://agentmods.dev/badge/commands/taylorbrook/max-msp_cc_framework/max-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,050 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.01050
Opus 5.5 $0.00004 $0.00420
Sonnet 5.5 $0.00002 $0.00210
Haiku 4.5 $0.00001 $0.00105

Measured 6d ago against content hash 901f95319681, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

max-test 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 6d 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.

.claude/commands/max-test.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/max-test

Generate a manual test checklist for patches in the active project, then record test results after the user runs them in MAX.

Behavior

  1. Load active project -- read patches/.active-project.json for the current project. If no active project, prompt the user.

  2. Identify target patches:

    • If a patch name is provided, locate that specific .maxpat file in generated/
    • If no name provided, find all .maxpat files in the project's generated/ directory
  3. Generate test checklist -- for each patch, call generate_test_checklist(patch_dict, patch_name, patch_path="") from src.maxpat.testing:

    • The checklist is based on detected objects: audio objects get signal flow tests, MIDI objects get note tests, UI objects get interaction tests
    • Each checklist item describes what to do in MAX and what to expect
  4. Display checklist -- present the test checklist to the user in a clear, numbered format:

    Test Checklist for: {patch-name}
    ================================
    [ ] 1. Open patch in MAX -- verify it loads without errors
    [ ] 2. {test item based on detected objects}
    [ ] 3. {test item based on detected objects}
    ...
    
  5. Record results -- after the user reports which tests passed/failed, call save_test_results(project_dir, test_name, results_md) from src.maxpat.testing to persist the results. It overwrites a same-named file, so name it v<version>-<slug>-checklist (version from get_version(project_dir)). Commit the results file by explicit path: auto_commit_patch(project_dir, base_dir, description="test results v<version> <slug>", files=[str(path)]); it raises RuntimeError on any git failure, so report that to the user (the results file is written but not committed).

  6. Record confirmations -- whenever the user confirms in MAX that a feature works (a passing checklist item, or in conversation, including after a /max-iterate fix), record it:

    path = record_confirmation(project_dir, feature, evidence, version=version, max_version="9.2.0", files=["generated/<name>.maxpat"])
    
    • evidence is the user's own words; feature is one short line.
    • This writes test-results/v<version>-<slug>-confirmed.md (<date>-<slug>-confirmed.md for an unversioned project), never overwrites an earlier confirmation (-2, -3, ...), and commits only that path.
    • It refuses private paths (/Users/, /home/, ~/.claude, memory-note filenames) and files outside the project.

Read the full file on GitHub · 81 lines

Changes

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.

  1. 6d ago Changed 901f95319681
  2. 7d ago Changed · +21 lines 122e0fbc83f7
  3. 2mo ago First seen · 60 lines · 11 tokens per session scan A ec534c720df7

Subscribe to this mod's changes

max-test is a command published in the GitHub repository taylorbrook/MAX-MSP_CC_Framework (46 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 1,050 once invoked, about $0.0000 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.