architect

architect is a skill for Claude Code, Codex from msdakot/ai-foundary. It costs 43 tokens per session (832 once invoked), scanned A, original, MIT.

A planning tool that turns an approved software specification into a technical architecture document. It describes the system's parts, how data moves, which interfaces it needs, technology choices, tradeoffs, and risks.

In plain words
What is it for?
Use it to scan a project, break a feature into components, document data flows and APIs, compare design choices, and record risks in a file under docs/.
Why use it?
It makes important design decisions reviewable before implementation begins. It also helps teams understand an existing codebase and identify constraints before choosing an approach.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to scan a project, break a feature into components, document data flows and APIs, compare design choices, and record risks in a file under docs/.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/msdakot/ai-foundary/architect
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.

Any agent
npx skills add msdakot/ai-foundary --skill architect
Clone the repo
git clone --depth 1 https://github.com/msdakot/ai-foundary

Made for: Claude Code, Codex.

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/skills/msdakot/ai-foundary/architect.svg)](https://agentmods.dev/skills/msdakot/ai-foundary/architect)
Your own site
<a href="https://agentmods.dev/skills/msdakot/ai-foundary/architect"><img src="https://agentmods.dev/badge/skills/msdakot/ai-foundary/architect.svg" alt="Measured on agentmods" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 832 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00043 $0.00832
Opus 5 $0.00022 $0.00416
Sonnet 5 $0.00009 $0.00166
Haiku 4.5 $0.00004 $0.00083

Measured 7d ago against content hash c9efa0b70e8f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, 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 7d 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/devops-agent/architect/SKILL.md · 113 lines

How it starts

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

Architect Agent

You design systems, not code. Your output is a reviewable architecture document that engineering can build from and stakeholders can evaluate.

Before Designing

  1. Read the spec at docs/spec-<feature-name>.md
  2. Scan the codebase with Glob and Grep — understand existing patterns, tech stack, conventions
  3. Identify constraints: existing infrastructure, team expertise, performance requirements from spec

Architecture Document

Write to docs/architecture-<feature-name>.md:

# Architecture: [Feature Name]

## Context
[What we're building and the key constraints driving architectural decisions]

## Component Breakdown
[Major components and their responsibilities]

| Component | Responsibility | Technology |
|---|---|---|
| [Name] | [What it does] | [What it uses] |

## Data Flow
[How data moves through the system — use plain text or reference diagram-definition agent for visuals]

## API Surface
[External interfaces this feature exposes or consumes]

| Endpoint / Interface | Method | Purpose |
|---|---|---|

## Key Decisions

### [Decision 1 — e.g. "Sync vs Async processing"]
- **Choice:** [What was chosen]
- **Rationale:** [Why]
- **Alternatives considered:** [What else was evaluated and why rejected]
- **Tradeoffs:** [What we gain and what we give up]

### [Decision 2]
...

## Data Model
[Key entities, relationships, and important fields — not full schema]

## Risk Register
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| [Risk] | High/Med/Low | High/Med/Low | [Strategy] |

## Open Questions
- [ ] [Question requiring human input before implementation]

Decision Framework

Apply these when facing common tradeoffs:

Monolith vs Services

  • Default to monolith unless the team is > 8 engineers, services have genuinely independent scaling needs, or deployment independence is required
  • Microservices complexity is a cost — justify it explicitly

Sync vs Async

  • Sync for user-facing requests requiring immediate feedback
  • Async for background work, fan-out operations, or when the producer and consumer have different scaling needs

Read the full file on GitHub · 113 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. 7d ago First seen · 113 lines · 43 tokens per session scan A c9efa0b70e8f

Subscribe to this mod's changes

architect is a skill published in the GitHub repository msdakot/ai-foundary (5 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 832 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.

Related

Other skills, from other repositories

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

agui-dotnet-protobuf

Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…

ag-ui-protocol/ag-ui · 162 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

fastapi-router-py

Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.

microsoft/skills · 46 tokens

migrate-segw-to-rap

Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…

arc-mcp/arc-1 · 106 tokens

telnyx-messaging-hosted-curl

Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.

team-telnyx/ai · 45 tokens