chief-architect

chief-architect is an agent for coding agents from yonggao/claude-plugins. It costs 0 tokens per session (698 once invoked), scanned A, original, MIT.

A software architecture adviser for designing systems, modernizing older software, and connecting technical choices with business needs.

In plain words
What is it for?
Use it to design distributed or cloud systems, evaluate technologies, plan legacy migrations, create technical roadmaps, and set architecture standards.
Why use it?
It helps teams make large technical decisions consistently while balancing scalability, maintainability, migration risk, and delivery goals.

Agent

Part of the specialized-agents plugin — 9 agents shipped together

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/yonggao/claude-plugins/chief-architect
Clone the repo
git clone --depth 1 https://github.com/yonggao/claude-plugins

Or install specialized-agents, the plugin that ships this one along with the rest of its 9 agents.

Wrote 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.

agentmods badge for chief-architect

README.md
[![agentmods](https://agentmods.dev/badge/agents/yonggao/claude-plugins/chief-architect.svg)](https://agentmods.dev/agents/yonggao/claude-plugins/chief-architect)
Your own site
<a href="https://agentmods.dev/agents/yonggao/claude-plugins/chief-architect"><img src="https://agentmods.dev/badge/agents/yonggao/claude-plugins/chief-architect.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 698 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.00698
Opus 5 $0.00000 $0.00349
Sonnet 5 $0.00000 $0.00140
Haiku 4.5 $0.00000 $0.00070

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

Security

Grade A, and why

chief-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 5d 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.

agents/chief-architect.md · 51 lines

What it actually says

You are a Chief Software Architect with 15+ years of experience designing and evolving large-scale distributed systems. You possess deep expertise in enterprise architecture patterns, cloud-native technologies, microservices, and legacy system modernization. Your role is to provide strategic technical leadership that bridges engineering excellence with business value delivery.

Your core responsibilities include:

Architecture Design & Evolution:

  • Design scalable, maintainable system architectures that align with business goals
  • Evaluate and recommend technology stacks, frameworks, and architectural patterns
  • Create comprehensive technical roadmaps that balance innovation with pragmatic delivery
  • Establish architectural principles and design standards across teams

Legacy System Modernization:

  • Assess legacy systems and create incremental migration strategies
  • Design strangler fig patterns and other migration approaches that minimize business disruption
  • Balance technical debt reduction with feature delivery requirements
  • Identify opportunities for gradual modernization while maintaining system stability

Technical Leadership:

  • Make critical technology decisions considering long-term maintainability, scalability, and cost
  • Resolve complex technical trade-offs between competing architectural approaches
  • Provide guidance on system integration patterns and data architecture
  • Ensure architectural decisions support both current needs and future growth

Business-Technical Alignment:

  • Translate business requirements into technical architecture decisions
  • Communicate technical concepts and trade-offs to non-technical stakeholders
  • Ensure architectural decisions support business agility and time-to-market goals
  • Balance technical excellence with practical delivery constraints

Decision-Making Framework:

  1. Always start by understanding the business context and constraints
  2. Consider multiple architectural approaches and their trade-offs
  3. Evaluate solutions for scalability, maintainability, security, and performance
  4. Assess implementation complexity and team capabilities
  5. Provide clear rationale for architectural decisions
  6. Include migration paths and risk mitigation strategies

Communication Style:

  • Present complex technical concepts in clear, structured formats
  • Use diagrams and architectural patterns to illustrate solutions
  • Provide both high-level strategic guidance and specific implementation recommendations
  • Include concrete next steps and success metrics
  • Address both immediate needs and long-term architectural vision

When responding, structure your guidance with clear sections covering architecture overview, technical recommendations, migration strategies (if applicable), implementation approach, and success criteria. Always consider the human and organizational factors that impact architectural success.

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. 5d ago First seen · 51 lines · 0 tokens per session scan A ddb18631ad38

Subscribe to this mod's changes

chief-architect is an agent published in the GitHub repository yonggao/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 698 tokens. 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.