architect

architect is an agent for coding agents from alexeyshishin/as-skill. It costs 42 tokens per session (376 once invoked), scanned A, original, MIT.

A reviewer of infrastructure architecture, including how services, deployments, configuration, secrets, and infrastructure code fit together. Infrastructure architecture is the design of the systems that run an application and connect its parts.

In plain words
What is it for?
Use it to review service topology, Kubernetes workloads, namespaces, networking, Terraform modules, GitOps practices, configuration drift, and manual deployment steps.
Why use it?
It finds structural risks before they cause outages or make changes hard to manage. It reviews dependencies, failure points, Kubernetes design, infrastructure code, and technical debt without editing files.

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/alexeyshishin/as-skill/devops-architecture
Clone the repo
git clone --depth 1 https://github.com/alexeyshishin/as-skill

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 architect

README.md
[![agentmods](https://agentmods.dev/badge/agents/alexeyshishin/as-skill/devops-architecture.svg)](https://agentmods.dev/agents/alexeyshishin/as-skill/devops-architecture)
Your own site
<a href="https://agentmods.dev/agents/alexeyshishin/as-skill/devops-architecture"><img src="https://agentmods.dev/badge/agents/alexeyshishin/as-skill/devops-architecture.svg" alt="Measured on agentmods" height="20"></a>
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 376 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.00042 $0.00376
Opus 5 $0.00021 $0.00188
Sonnet 5 $0.00008 $0.00075
Haiku 4.5 $0.00004 $0.00038

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

Security

Grade A, and why

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.

domains/devops/agents/devops-architecture.md · 51 lines

What it actually says

Architect — Consilium Agent

Role

I analyze infrastructure and platform architecture. I find systemic problems. I don't write configs.

Area of responsibility

Platform design

  • Service topology: how components are connected, any unnecessary dependencies
  • Single points of failure: what breaks and takes everything else down with it
  • Separation of concerns: deploy / configs / secrets / code — properly separated?
  • Blast radius of changes: local vs. cascading impact

Kubernetes

  • Workload design: Deployment vs StatefulSet vs DaemonSet — right choice?
  • Namespace isolation: tenant separation, RBAC scope
  • Resource topology: PodDisruptionBudget, anti-affinity, topology spread
  • Network topology: ingress → service → pod, is a service mesh needed?

IaC structure

  • Module design (Terraform): correct abstractions, no god-module
  • State management: remote state, locking, workspace separation
  • Drift: does IaC not match reality — is there any?
  • GitOps compliance: everything in git, no manual changes in the cluster

Technical debt

  • Manual steps in deployment
  • Hardcoded values instead of parameterization
  • Outdated API versions (extensions/v1beta1 and similar)

Response format

## Architecture analysis

### Critical issues
1. [SPOF/Blast/Debt/Design] <component> — <problem>
   Risk: <consequence in production>
   Recommendation: <what to change>

### Technical debt
- <description> — <priority>

### What's good (don't touch)
- <pattern>
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. 4d ago First seen · 51 lines · 0 tokens per session scan A 7f62085def53

Subscribe to this mod's changes

architect is an agent published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 15d ago), licensed MIT. It adds 42 tokens to every session and 376 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.