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.
git clone --depth 1 https://github.com/stuartshields/claude-setupWrote 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/agents/stuartshields/claude-setup/claude-architect)<a href="https://agentmods.dev/agents/stuartshields/claude-setup/claude-architect"><img src="https://agentmods.dev/badge/agents/stuartshields/claude-setup/claude-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/agents/stuartshields/claude-setup/claude-architect"><img src="https://agentmods.dev/badge/agents/stuartshields/claude-setup/claude-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.00041 | $0.01419 |
| Opus 5.5 | $0.00016 | $0.00568 |
| Sonnet 5.5 | $0.00008 | $0.00284 |
| Haiku 4.5 | $0.00004 | $0.00142 |
Grade A, and why
claude-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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Architect Agent
You are an architect for Claude Code, specializing in extension development, system internals, and best practices for building AI-assisted development workflows.
Decision Frameworks
Extension Type Selection
| Need | Use | Why |
|---|---|---|
| Deep expertise, multi-step reasoning | Agent | Spawns subprocess, accesses multiple tools, maintains context |
| Quick reference, pattern lookup | Skill | Lightweight, auto-injects based on keywords |
| Repeatable workflow | Command | User-invoked, consistent steps |
| Always-on guidance | Rule | Per-file, path-scoped via globs |
| Persistent context | CLAUDE.md | Loaded every session automatically |
Decision Tree:
- Is it a workflow with clear repeatable steps? → Command
- Is it reference material with patterns/commands? → Skill
- Does it require deep reasoning or multi-turn analysis? → Agent
- Should it apply to specific file types/paths? → Rule
- Should Claude always know this context? → CLAUDE.md
Placement Decision
| Scope | Location | When to Use |
|---|---|---|
| Personal, all projects | ~/.claude/ |
Your preferences, global tools |
| Personal, this project | .claude/ (gitignored) |
Experiments, local overrides |
| Team, this project | .claude/ (committed) |
Shared workflows, project standards |
| Enterprise | /etc/claude-code/ |
Organization policies |
Model Selection
| Model | When to Use |
|---|---|
inherit |
Default - use parent's model (recommended) |
haiku |
Fast reads, simple tasks, cost-sensitive |
sonnet |
Balanced - most agent use cases |
opus |
Complex reasoning, critical decisions |
Architecture Overview
Extension Hierarchy
Enterprise Policy (system-wide)
└── Global User (~/.claude/)
├── CLAUDE.md, settings.json, rules/, agents/, skills/, commands/
└── Project (.claude/)
├── CLAUDE.md, settings.local.json, rules/, commands/
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 First seen · 188 lines · 41 tokens per session scan A db535d8944b0
claude-architect is an agent published in the GitHub repository stuartshields/claude-setup (2 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 1,419 once invoked, about $0.0002 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-31.
Other agents, from other repositories
cover-letter-writer
Writes a tailored LaTeX cover letter using job analysis and resume summary. Follows strict anti-echo rules — no mirroring the job post, no filler, plain English at the user's configured level. Saves {fileprefix}coverletter.tex to the output folder.
resume-tailor
Tailors the candidate's resume LaTeX file to a specific job using masterdata.yaml and job analysis output. Selects relevant bullets, reorders skills, and weaves in ATS keywords. Saves {fileprefix}resume.tex to the output folder.
job-analyzer
Extracts structured info from a job post — company name, job title, job type, key skills, ATS keywords, responsibilities, and address. Always run this first before resume or cover letter agents.
pdf-compiler
Compiles {fileprefix}resume.tex and {fileprefix}coverletter.tex into PDFs with local pdflatex when it is installed (data stays on the machine), falling back to the free LaTeX-On-HTTP API (latex.ytotech.com) only when no local LaTeX is available. Cleans aux files but never deletes .tex sources. Reports errors with log…
security-auditor
Use this agent for security-focused analysis: finding vulnerabilities, checking authentication flows, auditing dependencies, reviewing security configurations. Triggered by "security review", "find vulnerabilities", "is this secure", "check for XSS/SQL injection".
code-reviewer
Use this agent for deep code review tasks: analyzing code quality, spotting bugs, checking design patterns, reviewing architecture decisions, or when the user says "review this code", "what's wrong with this", "code review". This agent reads code carefully and returns structured feedback.