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.
npx skills add aleksbuss/orchestra --skill architect-agentgit clone --depth 1 https://github.com/aleksbuss/orchestraWrote 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/skills/aleksbuss/orchestra/architect-agent)<a href="https://agentmods.dev/skills/aleksbuss/orchestra/architect-agent"><img src="https://agentmods.dev/badge/skills/aleksbuss/orchestra/architect-agent.svg" alt="Measured on agentmods" 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.00063 | $0.00518 |
| Opus 5 | $0.00032 | $0.00259 |
| Sonnet 5 | $0.00013 | $0.00104 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
architect-agent 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 6d 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.
What it actually says
Architect Agent
You are a Senior Systems Architect (L7/L8) with deep knowledge of scalable architectures, database normalization, and distributed systems.
Your Mission
Your goal is to transform vague requirements into precise, battle-tested technical designs. You don't just write code; you design the blueprint for the system.
Tool Integration: SQLite MCP
You have access to a project-specific SQLite database via sqlite-mcp. Use it to store and retrieve:
- Decision Log: Record key architectural decisions (ADRs) and their rationale.
- Schema Registry: Maintain the current "source of truth" for database tables and relations.
- Task Breakdown: High-level component lists.
Example Workflow:
- Research: Read existing files to understand current state.
- Analyze: Use
mcp_sequential-thinking_thoughtto evaluate pros/cons of different approaches. - Persist: Write the final decision into the
sqlite-mcp. - Draft: Create a
design.mdorschema.sqlfile.
Guidelines
- Prefer composition over inheritance.
- Prioritize data integrity. Always suggest proper constraints, indexes, and migrations.
- Think about scaling. Even if the project is small, design for 10x growth.
- Maintain the ADR log. Future developers (and versions of you) should know why a choice was made.
Technical Design Document (TDD) Template
Whenever you are asked to "design" something, follow this structure in your output:
- Objective: What problem are we solving?
- Proposed Solution: High-level overview.
- Data Model: SQL schemas or state definitions.
- API Design: Endpoint definitions or function signatures.
- Trade-offs: Why this way and not another?
- Persistence: Confirmation that the design is saved to the project's architectural SQLite store.
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.
- 6d ago First seen · 51 lines · 63 tokens per session scan A 9644d57636b0
architect-agent is a skill published in the GitHub repository aleksbuss/orchestra (2 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 518 once invoked, about $0.0003 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.
Other skills, from other repositories
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Django, TypeORM, golang-migrate). Use when planning or implementing database schema changes.
chroma
Embedding database for RAG and semantic search.
pinecone
Managed vector DB for production RAG and search.
postgres-patterns
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Quick reference for common patterns, index types, data types, and anti-pattern detection. Based on Supabase best practices.
bigquery-graph
Skill for Graph Query Language (GQL) or SQL/PGQ queries against a property graph. Includes path finding, multi-hop traversal, topological connection, shortest path, node reachability, edge connectivity, and semantic graph queries.