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 ApexIQ/skillsmith --skill architectgit clone --depth 1 https://github.com/ApexIQ/skillsmithWrote 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/apexiq/skillsmith/architect)<a href="https://agentmods.dev/skills/apexiq/skillsmith/architect"><img src="https://agentmods.dev/badge/skills/apexiq/skillsmith/architect.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.00033 | $0.01869 |
| Opus 5 | $0.00016 | $0.00934 |
| Sonnet 5 | $0.00007 | $0.00374 |
| Haiku 4.5 | $0.00003 | $0.00187 |
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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🏗️ Architect — System Design Decisions
Philosophy: Architecture is the set of decisions you wish you could get right early. Every design choice is a tradeoff — name the tradeoff explicitly or you'll discover it in production.
1. When to Use This Skill
- Designing a new system or service from scratch
- Choosing between architectural patterns (monolith vs microservices, etc.)
- Making database or infrastructure decisions
- Defining API contracts and service boundaries
- Evaluating build-vs-buy decisions
- Scaling an existing system
2. The Architecture Decision Framework
Step 1: Context Gathering
Before designing, answer these questions:
| Category | Questions |
|---|---|
| Users | Who uses this? How many concurrent? Growth rate? |
| Data | How much data? Read-heavy or write-heavy? Consistency requirements? |
| Reliability | What's the cost of downtime? Required uptime SLA? |
| Team | How many engineers? What expertise exists? |
| Timeline | MVP deadline? When does it need to scale? |
| Budget | Cloud spend constraints? Licensing constraints? |
Step 2: Architecture Decision Record (ADR)
For every significant decision, write an ADR:
# ADR-001: Use PostgreSQL over MongoDB for User Data
## Status: Accepted
## Date: 2026-03-25
## Context
We need a database for user data with complex relationships (users → teams → projects → permissions). Expected scale: 100K users in Year 1, 1M in Year 3.
## Decision
Use PostgreSQL with row-level security.
## Tradeoffs Considered
| Option | Pros | Cons |
|--------|------|------|
| PostgreSQL | ACID, relations, mature, RLS | Horizontal scaling harder |
| MongoDB | Flexible schema, easy horizontal | No joins, consistency tradeoffs |
| DynamoDB | Infinite scale, serverless | Vendor lock-in, complex queries expensive |
## Consequences
- ✅ Strong consistency guarantees for permission checks
- ✅ Team has PostgreSQL experience
- ⚠️ Will need read replicas at ~500K users
- ⚠️ Schema migrations require coordination
## Review Date: 2026-09-25
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.
- 7d ago First seen · 184 lines · 33 tokens per session scan A 46bc526e931e
architect is a skill published in the GitHub repository ApexIQ/skillsmith (5 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 1,869 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.
Other skills, from other repositories
pptx
Extract text from Microsoft PowerPoint presentations.
xlsx
Extract data from Excel and CSV files.
agent-teams
Multi-agent team orchestration with native Agent Teams. Trigger when the user wants to launch a team of agents, coordinate parallel work with inter-agent communication, or use swarm mode.
ops-infra-code
Infrastructure as Code with Terraform/OpenTofu. Trigger to create modules, configure backends, write idiomatic HCL, or audit infrastructure.
ops-proxmox
Proxmox VE infrastructure with Terraform (VMs, LXC, network, storage, backup).
Read, create and manipulate PDF files — extract text and tables, merge, split, rotate, reorder and delete pages, read and fill AcroForm fields, add or strip metadata, encrypt and decrypt, and generate new PDFs from HTML or from scratch. Also covers rasterising pages to images so a PDF can actually be looked at, and…