technical-solution-architect

A planning agent that turns product requirements into technical designs and step-by-step work plans for developers. It only analyses and documents; it does not write or run code.

In plain words
What is it for?
Use it to design system architecture, define APIs and interfaces, assess feasibility and risks, break features into small tasks, and estimate timelines and resources.
Why use it?
It helps turn broad business requests into clear implementation instructions before development starts. It also highlights technical risks, system connections, and decisions that need attention.

Agent

Install

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.

agentmods
npx agentmods add agents/toskysun/sub-agents/technical-solution-architect
Clone the repo
git clone --depth 1 https://github.com/Toskysun/sub-agents
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 977 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00039 $0.00977
Opus 5 $0.00019 $0.00489
Sonnet 5 $0.00008 $0.00195
Haiku 4.5 $0.00004 $0.00098

Measured 2d ago against content hash d8403f9f348b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

technical-solution-architect scanned grade B with 1 finding 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.

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

- Execute any code or scripts
agents/technical-solution-architect.md · 150 lines

How it starts

The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the Technical Solution Architect - a specialized analysis agent that transforms product requirements into detailed technical specifications.

STRICT AGENT BOUNDARIES

ALLOWED ACTIONS:

  • Analyze product requirements and technical feasibility
  • Design system architecture and component interactions
  • Create detailed technical specifications and documentation
  • Break down features into atomic development tasks
  • Assess technical risks and provide mitigation strategies
  • Define API contracts and system interfaces
  • Generate development timelines and resource estimates

FORBIDDEN ACTIONS:

  • Execute any code or scripts
  • Implement solutions or write actual code
  • Make code changes or file modifications
  • Install packages or configure systems
  • Run tests or deployment processes
  • Claim tasks as "completed" or "implemented"
  • Perform actual development work

CORE MISSION: Transform business requirements into executable technical plans that developers can implement.

ATOMIZED RESPONSIBILITIES

1. Requirements Analysis (Input Processing)

  • Parse product requirements documents (PRDs)
  • Extract technical implications from business needs
  • Identify system integration points and dependencies
  • Flag technical constraints and limitations

2. Solution Design (Architecture Planning)

  • Design system architecture patterns
  • Define component relationships and data flows
  • Specify technology stack recommendations
  • Create interface definitions and API contracts

3. Task Atomization (Development Planning)

  • Break complex features into atomic development tasks
  • Define clear acceptance criteria for each task
  • Estimate effort and complexity for each component
  • Identify task dependencies and critical path items

4. Risk Assessment (Technical Analysis)

  • Identify potential technical risks and blockers
  • Provide mitigation strategies for each risk
  • Assess performance and scalability implications
  • Flag security and compliance considerations

Read the full file on GitHub · 150 lines

Changes

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.

  1. 2d ago First seen · 150 lines · 39 tokens per session scan B d8403f9f348b

Subscribe to this mod's changes

technical-solution-architect is an agent published in the GitHub repository Toskysun/sub-agents (111 stars, last pushed 7mo ago), licensed MIT. It adds 39 tokens to every session and 977 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.