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/timothywarner-org/claude-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/commands/timothywarner-org/claude-architect/add-registry)<a href="https://agentmods.dev/commands/timothywarner-org/claude-architect/add-registry"><img src="https://agentmods.dev/badge/commands/timothywarner-org/claude-architect/add-registry/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/commands/timothywarner-org/claude-architect/add-registry"><img src="https://agentmods.dev/badge/commands/timothywarner-org/claude-architect/add-registry.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.00007 | $0.00601 |
| Opus 5 | $0.00003 | $0.00300 |
| Sonnet 5 | $0.00001 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
add-registry 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 9d 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.
This is a copy
100% identical to add-registry — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a new entry to registry.yaml for the notebook specified in the prompt above.
Instructions
- Read the notebook at the specified path to understand its content
- Check author exists in
authors.yaml:- Ask the user for the GitHub username of the notebook author
- Read
authors.yamland check if that username exists as a key - If the author does NOT exist, ask the user for their details and add them to
authors.yaml:- name: Full display name
- website: GitHub profile URL or personal website
- avatar: Use
https://github.com/<username>.pngas default
- Generate the registry entry with these fields:
Required Fields
- title: Extract from the notebook's first heading or create a concise, descriptive title
- description: Write a brief 1-2 sentence description summarizing what the notebook teaches
- path: The notebook path relative to the repository root
- authors: Use the GitHub username from step 2
- date: Use today's date in YYYY-MM-DD format
- categories: Select 1-2 appropriate categories from this list:
- Agent Patterns
- Claude Agent SDK
- Cybersecurity
- Evals
- Fine-Tuning
- Multimodal
- Integrations
- Observability
- RAG & Retrieval
- Responses
- Skills
- Thinking
- Tools
Style Guidelines
- Title should be concise but descriptive (see existing entries for examples)
- Description should be ~15-20 words, focusing on what the user will learn/build
- Choose categories that best match the notebook's primary focus
Output
- If author is new, show the proposed
authors.yamlentry for review and add it after approval - Show the user the proposed
registry.yamlentry for review - After user approval, use the Edit tool to append the entry to
registry.yaml - Maintain alphabetical ordering by path within the file, or append to the end if unclear
Example Entry Formats
authors.yaml (only if new author)
github-username:
name: Full Name
website: https://github.com/github-username
avatar: https://github.com/github-username.png
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.
- 9d ago First seen · 74 lines · 7 tokens per session scan A 602e2db272ff
add-registry is a command published in the GitHub repository timothywarner-org/claude-architect (81 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 601 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to add-registry, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
explore
Command "explore" from aderegil/claude-certified-architect, covering context: fork and allowed-tools: read, grep, glob.
review
Review the file at $ARGUMENTS for code quality issues.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
export-closedloop-learnings
Exports pending ClosedLoop learnings to global location with deduplication.
spreadsheet-audit
Perform a 6-step audit of an Excel spreadsheet for formula correctness, formatting consistency, data integrity, boss-auditable simplicity, and spec compliance. Uses the excel-screenshot MCP server tools — no Excel installation required.
research-verify
Verify existing research findings against independent primary sources. Upgrades confidence from 'sources agree' to 'independently verified.'.