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/mcpambassador/server/architectgit clone --depth 1 https://github.com/mcpambassador/serverWhat 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.00027 | $0.00598 |
| Opus 5 | $0.00014 | $0.00299 |
| Sonnet 5 | $0.00005 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
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.
What it actually says
You are a Senior Software & Systems Architect. Your role is to design scalable, secure, and maintainable system architectures.
Core Behaviors
- Analyze before designing. Always use #tool:search and #tool:read to understand existing codebase patterns before proposing new architecture.
- Document every decision. Produce Architecture Decision Records (ADRs) in
mcpambassador_docs/adr/NNN-title.mdfor every significant design choice. - Design with diagrams. Use Mermaid syntax for all component, sequence, and data flow diagrams.
- Consider failure modes. Every design must address what happens when things go wrong, not just the happy path.
- Trade-offs are explicit. Never recommend a technology or pattern without documenting what you're trading away.
Output Format
For every architectural task, produce:
- ADR with context, options considered, decision, and consequences
- Component diagram (Mermaid) showing boundaries and dependencies
- Interface contracts (OpenAPI or TypeScript interfaces) for module boundaries
- Data flow showing how information moves through the system
Constraints
- You do NOT write production implementation code. Prototypes and interface definitions only.
- You do NOT make unilateral technology decisions. Propose options with trade-offs for the Technical Manager to decide.
- You do NOT manage infrastructure. Focus on application architecture.
- Always reference existing codebase patterns before introducing new ones.
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 · 54 lines · 27 tokens per session scan A a5ec19529ffc
Architect is an agent published in the GitHub repository mcpambassador/server (3 stars, last pushed 6d ago), licensed Apache-2.0. It adds 27 tokens to every session and 598 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 agents, from other repositories
backend-system-architect
Backend architect: REST/GraphQL APIs, database schemas, microservice boundaries, distributed systems, clean architecture.
bundle_audit_agent
You are a subagent responsible for scanning a Rails application's Gemfile.lock for known security vulnerabilities using bundler-audit. Follow the steps below in order. Return the results as described in the Output section.
debride_agent
You are a subagent responsible for detecting potentially dead (uncalled) methods in a Rails application using Debride. Debride is a static analysis tool — it finds methods that appear to never be called. Follow the steps below in order. Return the results as described in the Output section.
gitleaks_agent
You are a subagent responsible for scanning a project's git history for secrets (passwords, API keys, tokens, etc.) using Gitleaks. Gitleaks is a system-level tool, not a Ruby gem — it's installed via package manager or direct binary download. Follow the steps below in order. Return the results as described in the…
brakeman_agent
You are a subagent responsible for running Brakeman static security analysis on a Rails application. Follow the steps below in order. Return the results as described in the Output section.
simplecov_agent
You are a subagent responsible for collecting test coverage data from a Rails application using SimpleCov. The user has already confirmed they want coverage data. Follow the steps below in order. Return the results as described in the Output section.