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/massdriver-cloud/claude-plugins/test-upgradegit clone --depth 1 https://github.com/massdriver-cloud/claude-pluginsWhat 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.00018 | $0.00425 |
| Opus 5 | $0.00009 | $0.00212 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
test-upgrade 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
Upgrade Testing
Start the upgrade-tester agent to validate a bundle version upgrade against production-like configuration.
What This Does
- Identify instance - Instance slug specifies exactly which bundle deployment to clone (e.g.,
api-prod-database) - Fork environment -
fork_environmentcreates an isolated test environment carrying prod's component config (secrets/refs/defaults opt-in) - Verify the mirror -
compare_environmentsbetween prod and the fork - Adjust scale - Optionally
copy_instancewithoverridesto reduce non-critical dependency sizes - Baseline deploy (MCP) -
create_deployment+get_deployment_logs follow:true - Upgrade (MCP) -
update_instanceto the target version, redeploy, then audit withcompare_deployments - Report results - Summary of upgrade success/failure with recommendations
Usage
Specify the instance slug and target version:
/massdriver:test-upgrade api-prod-database 1.3.0
/massdriver:test-upgrade ecomm-production-redis 2.0.0
Instance slugs follow the format: {project}-{environment}-{component} (e.g., api-prod-database).
If the slug or version aren't specified, the agent will ask.
Instructions
Use the Task tool to spawn the upgrade-tester agent with the upgrade details. The agent will handle the interactive workflow.
Parse the arguments to extract:
- Instance slug (first argument) - identifies the specific instance to clone
- Target version (second argument) - the version to upgrade to
If arguments weren't provided, ask the user for the instance slug and target version.
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 · 50 lines · 18 tokens per session scan A 47dc4ad6eff6
test-upgrade is a command published in the GitHub repository massdriver-cloud/claude-plugins (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 18 tokens to every session and 425 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-31.
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.