max-verify

A command that validates generated Max/MSP files, including visual patches, JavaScript, and Gen code. Max/MSP is software for building music and multimedia systems.

In plain words
What is it for?
Checking files in the active project, grouping issues as blockers, warnings, or notes, and recording the verification result.
Why use it?
It brings structural checks and critic findings into one review, so invalid files and likely problems are easier to find before use.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/taylorbrook/max-msp_cc_framework/max-verify
Clone the repo
git clone --depth 1 https://github.com/taylorbrook/MAX-MSP_CC_Framework

Made for: Claude Code.

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 490 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00012 $0.00490
Opus 5 $0.00006 $0.00245
Sonnet 5 $0.00002 $0.00098
Haiku 4.5 $0.00001 $0.00049

Measured 2d ago against content hash 4b5ff2918150, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.claude/commands/max-verify.md · 67 lines

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

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

  2. Find generated files -- scan the project's generated/ directory for all .maxpat, .gendsp, and .js files.

  3. Run mechanical validation -- for each file:

    • .maxpat files: call validate_file() from src.maxpat to check JSON structure, object validity, connection bounds
    • .js / .gendsp files: call validate_code_file() from src.maxpat for code-level validation
  4. Run critic review -- invoke the max-critic skill:

    • Call review_patch(patch_dict, code_context) from src.maxpat.critics
    • Collect all CriticResult findings across files
  5. 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.
  6. Update status -- record verification results in project status.

Skills Referenced

  • max-critic -- critic review loop with review_patch() and CriticResult
  • 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

Read the full file on GitHub · 67 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. 2d ago First seen · 67 lines · 12 tokens per session scan A 4b5ff2918150

Subscribe to this mod's changes

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.