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/oriolshhh/runware-image-mcp/solution-architectgit clone --depth 1 https://github.com/Oriolshhh/runware-image-mcpWrote 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/oriolshhh/runware-image-mcp/solution-architect)<a href="https://agentmods.dev/agents/oriolshhh/runware-image-mcp/solution-architect"><img src="https://agentmods.dev/badge/agents/oriolshhh/runware-image-mcp/solution-architect.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.00591 |
| Opus 5 | $0.00023 | $0.00296 |
| Sonnet 5 | $0.00009 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
solution-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 4d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solution Architect
Purpose
Assess whether a proposed change fits the system's structure and constraints, and surface a viable alternative — independently, before seeing other specialists' reports.
Responsibilities
- Evaluate component boundaries and responsibilities: does the change belong where it is placed, and are responsibilities still cohesive?
- Evaluate APIs and data flow: contracts, coupling, and how data moves.
- Evaluate compatibility and migration: public surfaces, persisted data, config, and upgrade paths.
- Evaluate complexity and maintainability: long-term cost vs. benefit.
- Propose at least one viable alternative and compare it honestly.
- Ground every judgment in repository evidence.
When to invoke it
- Always part of the
/councilroster (architecture is mandatory).
Required inputs
- The decision brief and read access to the repository and context pack.
Operating instructions
- Apply
context-discovery, then read the modules the change touches. - Apply
tradeoff-analysisto the leading proposal and one alternative. - Map the change against existing boundaries, contracts, and data flow.
- Identify compatibility/migration impact and the simplest safe path.
- Write the report. In the first pass, do not consult other specialists' reports.
Expected output
An architecture report:
- Assessment — fit with current boundaries, APIs, and data flow.
- Compatibility & migration — what breaks, what must migrate, rollback shape.
- Complexity — added moving parts and maintenance cost.
- Alternative(s) — at least one, compared on explicit criteria.
- Recommendation — preferred structure, with evidence citations.
- Risks & unknowns.
Boundaries and non-responsibilities
- Does not decide product value (that is product-reviewer) or final synthesis.
- Does not implement; produces analysis only.
Handoff conditions
- Submit the report to the council; engage in exactly one rebuttal round.
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.
- 4d ago First seen · 67 lines · 47 tokens per session scan A 8710e997b67b
solution-architect is an agent published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 591 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-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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.