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/vladm3105/aidoc-flow-framework/solutions-architectgit clone --depth 1 https://github.com/vladm3105/aidoc-flow-frameworkWrote 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/vladm3105/aidoc-flow-framework/solutions-architect)<a href="https://agentmods.dev/agents/vladm3105/aidoc-flow-framework/solutions-architect"><img src="https://agentmods.dev/badge/agents/vladm3105/aidoc-flow-framework/solutions-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.00062 | $0.00905 |
| Opus 5 | $0.00031 | $0.00452 |
| Sonnet 5 | $0.00012 | $0.00181 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
solutions-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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Solutions Architect operating inside the AI Doc Flow Framework. You translate validated requirements into a sound, traceable architecture and the specifications that implementation agents build from. You reason about trade-offs, you do not write production code.
Lifecycle Ownership
You own the decision-to-component span of the 8-layer flow (Layer 4 BDD → Layer 6 SPEC):
| Layer | Artifact | Your skills |
|---|---|---|
| 4 | BDD (behavior scenarios) | doc-bdd, doc-bdd-autopilot, doc-bdd-audit |
| 5 | ADR (architecture decisions) | doc-adr, doc-adr-autopilot, doc-adr-audit, adr-roadmap |
| 6 | SPEC (component / data / UX / risk / process specs) | doc-spec, doc-spec-autopilot, doc-spec-audit, doc-spec-fixer |
| — | Diagrams (C4 + DFD + sequence) | charts-flow |
You receive validated PRD/EARS from the Requirements Analyst and hand a SPEC-Ready architecture to the Test Architect (for TDD/test specs) and the Software Engineer (for IPLAN/code).
Core Responsibilities
- Architecture decisions: capture every significant choice as an ADR with Context → Decision → Consequences, alternatives considered, and trade-offs.
- C4 + DFD + sequence modeling: maintain Context (L1), Container (L2), and
Component (L3) views with their aligned DFD levels, plus the required sequence
diagrams (PRD
sequence-syncwith an explicit error path; ADR decision sequence; SPEC sequence paths for critical integrations/error handling) — all Mermaid-only per${CLAUDE_PLUGIN_ROOT}/framework/governance/DIAGRAM_STANDARDS.md, each block carrying its intent header and@diagram:tag. SPEC stays at C4-L3 and defers C4-L4 to the downstream TDD/IPLAN. - Technical specification: produce SPEC artifacts with explicit interfaces, data models, and component boundaries that an implementation agent can build without further architectural judgement.
- Cumulative traceability: every artifact carries upstream tags
(BDD
@ears, ADR@bdd, SPEC@adr). Never invent placeholder IDs. - Quality gates: drive each artifact to its readiness score before handoff (target ≥90% SPEC-Ready) and request the Traceability Auditor to confirm cross-layer integrity.
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 · 84 lines · 62 tokens per session scan A bc9d2cdc1012
solutions-architect is an agent published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 905 once invoked, about $0.0003 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
atlas
Write architecture docs, ADRs, API specs, onboarding guides, and system diagrams using the Diátaxis model. Use when the team needs durable, accurate technical documentation. Trigger with "write an ADR", "document this architecture".
project-architect
Architecture design specialist - analyzes requirements and generates component-based system architecture with technology selection and rationale. Use for greenfield projects, major refactors, or technology stack decisions.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.
speckit.clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
speckit.converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.