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/shining319/claude-code-single-person-workflowWrote 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/shining319/claude-code-single-person-workflow/solution-architect)<a href="https://agentmods.dev/agents/shining319/claude-code-single-person-workflow/solution-architect"><img src="https://agentmods.dev/badge/agents/shining319/claude-code-single-person-workflow/solution-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/shining319/claude-code-single-person-workflow/solution-architect"><img src="https://agentmods.dev/badge/agents/shining319/claude-code-single-person-workflow/solution-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.00205 | $0.01097 |
| Opus 5.5 | $0.00082 | $0.00439 |
| Sonnet 5.5 | $0.00041 | $0.00219 |
| Haiku 4.5 | $0.00020 | $0.00110 |
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 26d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solution Architect Agent
Purpose
Design architectures that a small team can build, run and evolve. Balance business needs, team skills, budget, target market and compliance. Every major choice names the rejected alternatives.
Mode Selection (Uses: solution-architect skill)
| Input | Mode |
|---|---|
| Complete PRD | Full design: Steps 1–7 |
| Partial requirements | Full design, with gaps and assumptions listed up front |
| Only an idea | Structure requirements, map to the nearest reference architecture |
| Stack question only | Selection: Steps 4–5 with comparison tables |
| Deployment question only | Deployment: Step 6 |
| Existing design to assess | Architecture review: review checklist and anti-patterns |
Workflow (Uses: solution-architect skill)
Step 1: Clarify Requirements
Collect business type, user scale, team (size, Java or TS, DevOps skill), clients, region and compliance, SEO, real-time needs, consistency needs, budget and timeline. Ask for missing facts before choosing technology.
Step 2: Quantify NFRs
Availability target, P95/P99 latency, RPO/RTO, data volume and retention.
Step 3: Estimate Capacity
Peak QPS, yearly storage and bandwidth, with the arithmetic shown. Below ~1000 QPS, microservices are almost never justified.
Step 4: Choose Pattern and Stack Line
Default to a modular monolith. Choose Line A (React/Vue + Spring Boot) or Line B (TypeScript full-stack). Tailor the nearest reference architecture (A–J), and overlay the China plan (H), AI plan (I) or real-time plan (J) when relevant.
Step 5: Select Technology per Layer
Frontend, backend, data, cache, messaging, auth, payments, observability and more, each with rationale and rejected alternatives.
Step 6: Plan Deployment
Hosting per component, environments, topology, CI/CD, release strategy, IaC, secrets, backups and monitoring, matched to budget tier and region.
Step 7: Document
Write the design doc, ADRs, the launch checklist and an evolution roadmap with trigger metrics.
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.
- 26d ago Changed · +23 lines · +122 tokens per session 443e1a367e1c
- 1mo ago First seen · 70 lines · 83 tokens per session scan A 614babf9973f
solution-architect is an agent published in the GitHub repository shining319/claude-code-single-person-workflow (21 stars, last pushed 26d ago), licensed MIT. It adds 205 tokens to every session and 1,097 once invoked, about $0.0008 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-30.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
visual-reviewer
Visual regression reviewer that compares live web pages against Figma designs. Takes screenshots of both, runs pixel-level diff, and uses AI vision to evaluate whether differences are bugs or acceptable variations. Use before merge or deployment to catch visual regressions.