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-iterate.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-iterate)<a href="https://agentmods.dev/commands/taylorbrook/max-msp_cc_framework/max-iterate"><img src="https://agentmods.dev/badge/commands/taylorbrook/max-msp_cc_framework/max-iterate/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-iterate"><img src="https://agentmods.dev/badge/commands/taylorbrook/max-msp_cc_framework/max-iterate.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.00013 | $0.03904 |
| Opus 5.5 | $0.00005 | $0.01562 |
| Sonnet 5.5 | $0.00003 | $0.00781 |
| Haiku 4.5 | $0.00001 | $0.00390 |
Grade A, and why
max-iterate 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/max-iterate
Apply modifications to existing .maxpat patches using the analyze-first protocol. Reads the patch, shows a structural analysis, then makes surgical or section-level edits while preserving all existing objects and user positioning.
Behavior
-
Parse arguments for inline project switch -- before loading the active project, check if the first word of the argument string matches an existing project:
from src.maxpat.project import get_active_project, set_active_project, list_projects, update_status, bump_version projects = list_projects(base_dir) args = user_input.strip() first_word = args.split()[0] if args else "" # Case-insensitive match against known project directories matched_project = None for p in projects: if p.lower() == first_word.lower(): matched_project = p break if matched_project: set_active_project(matched_project, base_dir) change_description = " ".join(args.split()[1:]) # remaining text else: change_description = args # entire string is the description -
Parse flags -- extract workflow flags from the argument string before interpreting the change description:
- Scan
change_description(the text remaining after inline project switch parsing) for--full,--discuss,--research,--planand--fix --fullexpands to all three: discuss + research + plan--discuss,--research,--plancan be used individually or combined--fixswitches to Quick-fix mode (see "Quick-fix mode (--fix)" below) instead of steps 6-18- Strip all recognized flags from
change_descriptionso downstream steps see only the modification text - Store flags as booleans:
do_discuss,do_research,do_plan,do_fix
- Scan
-
Load active project -- read
patches/.active-project.jsonfor the current project (which may have just been set by the step above). If no active project, prompt the user. -
Auto-detect target .maxpat -- determine which patch file to edit:
- Single .maxpat in
generated/: use it automatically - Multiple .maxpat files: infer from the user's change description (match keywords to filenames)
- Ambiguous: ask the user which file to edit
- Single .maxpat in
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 · +1 lines df1f8ad5281d
- 7d ago Changed · +73 lines 1b65099f8dba
- 14d ago Changed 555a467fbe9b
- 15d ago Changed d99725ab20ab
- 2mo ago First seen · 184 lines · 13 tokens per session scan A cdfaef0a29db
max-iterate is a command published in the GitHub repository taylorbrook/MAX-MSP_CC_Framework (46 stars, last pushed 4d ago), licensed MIT. It adds 13 tokens to every session and 3,904 once invoked, about $0.0001 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.