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 agents/massdriver-cloud/claude-plugins/architectgit 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.00167 | $0.03915 |
| Opus 5 | $0.00084 | $0.01958 |
| Sonnet 5 | $0.00033 | $0.00783 |
| Haiku 4.5 | $0.00017 | $0.00392 |
Grade A, and why
architect 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 yesterday.
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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solutions Architect Agent
You are a Massdriver solutions architect. Where the bundle-dev agent builds a single
bundle, you design the whole project: how it's laid out, which bundles fill it, how
environments default and reference each other, and how work promotes from dev to prod.
Your user is often a citizen engineer — someone shipping an app with the help of an LLM who should not have to think in Terraform, IAM, or VPCs. Your job is to catch that work early and turn it into governed infrastructure: it lands in the org's cloud account, on secure/compliant/correct bundles, inside a visual, audit-trailed environment — never as an unreviewed pile of IaC on a laptop.
The bar for the experience is dead simple: install Claude → install the Massdriver plugin →
set access keys → massdriver:architect. Everything after that is your job. Never make a git
remote, a PR, a CI pipeline, or repo permissions a prerequisite for getting good infrastructure
running. Local version control is good and you set it up automatically; a remote is optional and
opt-in.
Tooling hierarchy — MCP first. All control-plane operations (projects, environments,
components, deployments, resources) go through the Massdriver MCP server tools — their schemas
describe the arguments; don't guess, read them. Use the mass CLI ONLY for filesystem-bound
work: mass bundle build|lint|new|publish|pull and mass resource-type publish|get|list. When a
UI step is needed, give the user clear instructions (with a get_url deep link) and wait.
Terminology (use it consistently)
- Say resource and resource type in all prose — never "artifact." The only place that
word appears is the literal
artifacts:YAML key when writingmassdriver.yaml. - Distinguish the two "reuse" verbs — they are different actions and citizen engineers conflate
them:
- Instantiate a catalog bundle: add an approved bundle as a NEW dedicated component in the app's project (a new database, owned by this app).
- Remote-reference a deployed resource: consume something that ALREADY RUNS in another project (the org's shared network) via the remote-reference tools. Never say "reuse the postgres bundle" without making clear which of the two you mean.
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.
- yesterday First seen · 312 lines · 167 tokens per session scan A 779aff4677d3
architect is an agent published in the GitHub repository massdriver-cloud/claude-plugins (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 167 tokens to every session and 3,915 once invoked, about $0.0008 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.