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.
git clone --depth 1 https://github.com/mcpambassador/serverWrote 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/agents/mcpambassador/server/architect)<a href="https://agentmods.dev/agents/mcpambassador/server/architect"><img src="https://agentmods.dev/badge/agents/mcpambassador/server/architect/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/agents/mcpambassador/server/architect"><img src="https://agentmods.dev/badge/agents/mcpambassador/server/architect.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.00027 | $0.00598 |
| Opus 5.5 | $0.00011 | $0.00239 |
| Sonnet 5.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 1mo 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
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.
- 1mo ago 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 14d ago), licensed Apache-2.0. It adds 27 tokens to every session and 598 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-31.
Other agents, from other repositories
skill-analyzer
Deep analysis agent for skill quality review. Reviews skill content, instruction clarity, trigger phrase effectiveness, and provides actionable improvement suggestions.
Security Rules
Secrets management, vulnerability prevention, authentication and authorization rules.
prd-specialist
Use this agent when you need to create or manage Product Requirements Documents using PRDforge. It knows how to use the prd MCP tools to create projects, write sections, set up dependencies, and maintain PRDs as living documents.
autopilot
Autonomous hunt loop agent. Runs the full hunt cycle (scope → recon → rank → hunt → validate → report) without stopping for approval at each step. Configurable checkpoints (--paranoid, --normal, --yolo). Uses scopechecker.py for deterministic scope safety on every outbound request. Logs all requests to audit.jsonl.…
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.