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 agentmods add commands/timothywarner-org/claude-architect/model-checkgit 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/model-check)<a href="https://agentmods.dev/commands/timothywarner-org/claude-architect/model-check"><img src="https://agentmods.dev/badge/commands/timothywarner-org/claude-architect/model-check.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.00008 | $0.00204 |
| Opus 5 | $0.00004 | $0.00102 |
| Sonnet 5 | $0.00002 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
model-check 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 5d 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 model-check — 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.
What it actually says
IMPORTANT: Only review the files explicitly listed in the prompt above. Do not search for or review additional files.
Review the specified changed files for Claude model usage.
First, fetch the current list of allowed models from: https://docs.claude.com/en/docs/about-claude/models/overview.md
Then check:
- All model references are from the current public models list
- Flag any deprecated models (older Sonnet 3.5, Opus 3 versions)
- Flag any internal/non-public model names
- Suggest using aliases ending in -latest for better maintainability
Provide clear, actionable feedback on any issues found.
IMPORTANT: Post your findings as a comment on the pull request using the command: gh pr comment $PR_NUMBER --body "your findings"
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.
- 5d ago First seen · 21 lines · 8 tokens per session scan A fa169bfa0f91
model-check is a command published in the GitHub repository timothywarner-org/claude-architect (80 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 204 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 model-check, 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.
README
Git workflow and quality assurance commands for the claude-skills repository.
agent-handoff
Wraps termlink agent contact so vendored Claude Code agents can hand off context to a peer agent in one command. Replaces the legacy remote push.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.