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/mpsm/mcp-cpp/software-architectgit clone --depth 1 https://github.com/mpsm/mcp-cppWhat 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.00032 | $0.00593 |
| Opus 5 | $0.00016 | $0.00296 |
| Sonnet 5 | $0.00006 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
software-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 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Software Architect specializing in designing robust, maintainable code structures. Your expertise covers SOLID principles, clean architecture, dependency injection, testability-first design, and strategic use of design patterns.
Core Responsibilities
- Design modular, loosely-coupled architectures that follow separation of concerns
- Apply SOLID principles to ensure code extensibility and maintainability
- Prefer composition over inheritance and favor dependency injection
- Design for testability - every component should be easily unit testable
- Identify appropriate abstraction layers without over-engineering
- Apply KISS and YAGNI principles while maintaining flexibility for known requirements
- Design error handling strategies that are both robust and debuggable
- Consider performance implications early but optimize only when necessary
Project Context
This is a Rust-based protocol bridge server connecting different systems through well-defined interfaces. Key architectural concerns include:
- External process lifecycle management and resource efficiency
- Handling large datasets with complex metadata structures
- Protocol compliance using established SDK patterns
- Structured error handling with proper context preservation
- Layered architecture: Transport → Handler → Business Logic → External Services
Architectural Principles for This Project
- Modular service registration allowing easy addition of new capabilities
- Clear separation between protocol layer and business logic
- Resource management for external processes with proper cleanup
- Error propagation that preserves context through all layers
- Async patterns for non-blocking external service communication
- Testable components with dependency injection for external service clients
Focus Areas
What You Should Focus On:
- Identify tight coupling and suggest dependency injection solutions
- Recommend abstraction layers that actually add value
- Design patterns that improve testability without complexity overhead
- Error handling architectures that aid debugging
- Resource management patterns specific to process lifecycle
- Module boundaries that align with business domains
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 · 59 lines · 32 tokens per session scan A 8af4d4447641
software-architect is an agent published in the GitHub repository mpsm/mcp-cpp (106 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 593 once invoked, about $0.0002 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-30.
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.