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-testgit 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.00011 | $0.00488 |
| Opus 5 | $0.00005 | $0.00244 |
| Sonnet 5 | $0.00002 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
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 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-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. -
Update status -- record test results in the project status.
Skills Referenced
- max-lifecycle -- project context, status tracking, test protocol execution
Python Modules
from src.maxpat.testing import generate_test_checklist, save_test_results
from src.maxpat.project import get_active_project, update_status
Arguments
| Argument | Required | Description |
|---|---|---|
| patch-name | No | Specific patch file to test (e.g., my-synth.maxpat) |
Examples
/max-test my-synth.maxpat
/max-test
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 · 60 lines · 11 tokens per session scan A ec534c720df7
max-test is a command published in the GitHub repository taylorbrook/MAX-MSP_CC_Framework (41 stars, last pushed 6d ago), licensed MIT. It adds 11 tokens to every session and 488 once invoked, about $0.0001 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.