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-verifygit 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.00012 | $0.00490 |
| Opus 5 | $0.00006 | $0.00245 |
| Sonnet 5 | $0.00002 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
max-verify 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/max-verify
Run the full validation pipeline and critic review on all generated files in the active project.
Behavior
-
Load active project -- read
patches/.active-project.jsonfor the current project. If no active project, prompt the user. -
Find generated files -- scan the project's
generated/directory for all.maxpat,.gendsp, and.jsfiles. -
Run mechanical validation -- for each file:
.maxpatfiles: callvalidate_file()fromsrc.maxpatto check JSON structure, object validity, connection bounds.js/.gendspfiles: callvalidate_code_file()fromsrc.maxpatfor code-level validation
-
Run critic review -- invoke the max-critic skill:
- Call
review_patch(patch_dict, code_context)fromsrc.maxpat.critics - Collect all
CriticResultfindings across files
- Call
-
Display results grouped by severity:
- Blockers -- must be fixed before the patch will work correctly. Suggest specific fixes.
- Warnings -- potential issues that may cause unexpected behavior. Annotate with explanation.
- Notes -- informational observations about style or best practices.
-
Update status -- record verification results in project status.
Skills Referenced
- max-critic -- critic review loop with
review_patch()andCriticResult - max-lifecycle -- project context and status updates
Python Modules
from src.maxpat import validate_file, validate_code_file
from src.maxpat.critics import review_patch, CriticResult
from src.maxpat.project import get_active_project, update_status
Arguments
None required. Verifies all generated files in the active project.
Examples
/max-verify
Output Format
Verification Results for: {project-name}
=========================================
{filename}:
BLOCKER: {description} -- Fix: {suggestion}
WARNING: {description}
NOTE: {description}
Summary: {blockers} blockers, {warnings} warnings, {notes} notes
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 · 67 lines · 12 tokens per session scan A 4b5ff2918150
max-verify is a command published in the GitHub repository taylorbrook/MAX-MSP_CC_Framework (41 stars, last pushed 6d ago), licensed MIT. It adds 12 tokens to every session and 490 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.