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 alonbaron/claude-skills --skill architectgit clone --depth 1 https://github.com/alonbaron/claude-skillsWrote 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/alonbaron/claude-skills/architect)<a href="https://agentmods.dev/skills/alonbaron/claude-skills/architect"><img src="https://agentmods.dev/badge/skills/alonbaron/claude-skills/architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/alonbaron/claude-skills/architect"><img src="https://agentmods.dev/badge/skills/alonbaron/claude-skills/architect.svg" alt="Reviewed on agentmods" width="80" 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.00096 | $0.02510 |
| Opus 5.5 | $0.00038 | $0.01004 |
| Sonnet 5.5 | $0.00019 | $0.00502 |
| Haiku 4.5 | $0.00010 | $0.00251 |
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 1mo 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
!ls -1 SOURCE_OF_TRUTH.md ARCHITECTURE_ROADMAP.md TODO_WORKFLOW.md CLAUDE.md docs/architecture 2>/dev/null || true
The line above lists which design docs already exist in this repo, so create-vs-audit mode is known before the first tool call.
Architect
Design and document the system before building it — in the house doc format, kept in sync at all times. Output is documents, not code.
Principles
Enforced in the docs: model first (data + invariants before framework) · enforce every invariant at the core, ideally at two boundaries (app-layer validation and a DB constraint) — never "the frontend handles it" · design failure paths as deliberately as happy paths · small, reversible, independently shippable steps · one source of truth — everything else derives from it and links back.
Proactive use
If a new app, feature, or workstream is starting and no current design docs exist, invoke this without being asked: announce in one line — "Running architect: " — and proceed. Never ask permission to run the skill; the 1–3 blocking questions below are still allowed.
The four artifacts (+ the modular set)
Authority flows top-down. A fact lives in exactly one place and is linked from everywhere else.
SOURCE_OF_TRUTH.md(apex) — the canonical, slow-changing truth: scope & non-goals · the domain model · the invariants and where each is enforced · the load-bearing decisions as mini-ADRs (decision · why · alternative rejected). If anything conflicts with this file, this file wins. Keep it tight — it is the contract, not the manual.ARCHITECTURE_ROADMAP.md— architecture + phased plan derived from the SoT. Header block (Version · Status · Owner), then §-numbered:0Executive context ·1Tech stack (Layer · Tech · Role table) ·2Data schema (low-level: columns, types, constraints, indexes, JSONB shapes, decision call-outs) ·3Backend (structure · services · API-contract table) ·4Frontend ·5Execution phases ·6Non-functional requirements.docs/architecture/00-index.md+01-…NN(larger projects only) — agent-friendly modular extracts of the roadmap sections. The index carries a File Map table (# · file · covers · roadmap §), a Dependency Graph (ASCII), and a Quick Reference ("I need to work on X → read these files").TODO_WORKFLOW.md— the task tracker. Status legend ([ ]·[IN PROGRESS]·[FINISHED - PENDING MERGE]·[MERGED/DONE]·[BLOCKED]); tasks grouped by phase; each row:# · Task · Architecture Ref (linked to the §/file) · Status · Branch. A task closed mid-phase leaves aLeft for <id>: ...note for whoever picks it up next.CLAUDE.md(project root) — the rules file Claude Code auto-loads: operating rules + the sync protocol (template below). One markdown file — no.clauderules, no.cursorrules, no import shim.
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.
- 1mo ago Changed · +28 lines · -19 tokens per session 2d712a0d42fd
- 1mo ago First seen · 164 lines · 115 tokens per session scan A 0194626f63d8
architect is a skill published in the GitHub repository alonbaron/claude-skills (13 stars, last pushed 3d ago), licensed MIT. It adds 96 tokens to every session and 2,510 once invoked, about $0.0004 per session on Opus 5.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
gemini
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini…
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
security-architecture-review
Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a…
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.