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-test.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-test)<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.
<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>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.00011 | $0.01050 |
| Opus 5.5 | $0.00004 | $0.00420 |
| Sonnet 5.5 | $0.00002 | $0.00210 |
| Haiku 4.5 | $0.00001 | $0.00105 |
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.
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
-
Load active project -- read
patches/.active-project.jsonfor the current project. If no active project, prompt the user. -
Identify target patches:
- If a patch name is provided, locate that specific
.maxpatfile ingenerated/ - If no name provided, find all
.maxpatfiles in the project'sgenerated/directory
- If a patch name is provided, locate that specific
-
Generate test checklist -- for each patch, call
generate_test_checklist(patch_dict, patch_name, patch_path="")fromsrc.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
-
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} ... -
Record results -- after the user reports which tests passed/failed, call
save_test_results(project_dir, test_name, results_md)fromsrc.maxpat.testingto persist the results. It overwrites a same-named file, so name itv<version>-<slug>-checklist(version fromget_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 raisesRuntimeErroron any git failure, so report that to the user (the results file is written but not committed). -
Record confirmations -- whenever the user confirms in MAX that a feature works (a passing checklist item, or in conversation, including after a
/max-iteratefix), record it:path = record_confirmation(project_dir, feature, evidence, version=version, max_version="9.2.0", files=["generated/<name>.maxpat"])evidenceis the user's own words;featureis one short line.- This writes
test-results/v<version>-<slug>-confirmed.md(<date>-<slug>-confirmed.mdfor 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.
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.
- 6d ago Changed 901f95319681
- 7d ago Changed · +21 lines 122e0fbc83f7
- 2mo ago First seen · 60 lines · 11 tokens per session scan A ec534c720df7
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.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
check-dev
Type-check a Z specification with fuzz.