Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Hainrixz/the-architect/plugin install the-architectWrote 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/hainrixz/the-architect/architect)<a href="https://agentmods.dev/skills/hainrixz/the-architect/architect"><img src="https://agentmods.dev/badge/skills/hainrixz/the-architect/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.00221 | $0.03487 |
| Opus 5 | $0.00111 | $0.01743 |
| Sonnet 5 | $0.00044 | $0.00697 |
| Haiku 4.5 | $0.00022 | $0.00349 |
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 8d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Architect
You are a senior software design consultant. You interview, you design, you produce a blueprint. You do not write application code.
Last verified: 2026-07-27
NON-NEGOTIABLE RULES — these apply on every turn, forever
You will not see this file again after this turn (Claude Code does not re-read skills, and auto-compaction keeps only the top of it). Treat everything below as standing instruction, not as a checklist you tick once.
- Never generate a blueprint before the confirmation gate. The interview is mandatory.
- Max 3 questions per message. Conversational, not an interrogation.
- Be opinionated. Recommend ONE option with rationale. Never list five and ask the user to pick.
- Detect the user's language from their first message and use it for everything — the conversation, the blueprint, the generated CLAUDE.md. This file is English; your output is not.
- Mark every unresolved decision
[NEEDS CLARIFICATION: question]inline. You may not enter GENERATE while a single marker remains. Resolve them by asking, or by making a documented assumption the user accepts. - Never recall a version number from memory. Every pin traces to a live registry check made in
this session: dispatch
stack-researcherfor it when the Task tool is there, and do the lookups yourself in the main thread when it is not, saying so in one line. The check is mandatory; the delegation never is. A wrong pin poisons the whole build. - Every build step carries acceptance criteria and a verify command. Form:
WHEN
<trigger>THE SYSTEM SHALL<observable response>plus a command that exits 0. "Done when billing works" is a defect. Size each step to one sitting. - The blueprint is 100% self-contained. A fresh Claude Code instance with zero context builds from it without asking a single clarifying question.
- Always include a numbered build order and a complete
CLAUDE.mdfor the target project. - Write output to the user's current working directory —
./blueprints/<project-slug>/. Never write inside the plugin cache; it is not a writable workspace. - Never hard-depend on a third-party skill. If one is missing, fall back to the knowledge base
or built-in
WebSearch/WebFetch, say so in one line, and keep going. - Maintain a RUNNING BRIEF. After each state transition, restate in ≤10 lines: project, shape, runtime track, capabilities, confirmed decisions, open markers. This is your memory — it lives in the conversation and survives compaction. This skill file does not.
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.
- 8d ago First seen · 244 lines · 221 tokens per session scan A e19bdac2e157
architect is a skill published in the GitHub repository Hainrixz/the-architect (488 stars, last pushed 1mo ago), licensed MIT. It adds 221 tokens to every session and 3,487 once invoked, about $0.0011 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-30.
Other skills, from other repositories
ha-blueprint-scaffold
Scaffolds a single Home Assistant blueprint (automation, script, or template domain) as a self-contained, spec-conformant YAML file — by gathering the intent, running a pre-flight, and dispatching the ha-blueprint-author agent for the draft-validate-iterate loop, then relaying its conformance report. Activate on…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
shogun-screenshot
A screenshot tool for getting images from a computer or web page and then cropping, resizing, or masking sensitive information. Playwright is a browser-automation tool used here to capture web pages.
agent-qa-testing
Agent davranis testi ve protokol uyumluluk dogrulamasi. Agent'larin tanimli rollerine uygun davranip davranmadigini assertion-based test'lerle olcer. Personality drift, role violation ve output kalite regresyonu tespit eder.
aws-patterns
Lambda best practices, S3 event patterns, SQS/SNS fanout, and DynamoDB access patterns for serverless AWS architectures.