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 agents/pymodel/claude-architect/claude-advisorgit clone --depth 1 https://github.com/PyModel/claude-architectWhat 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 | $0.00084 | $0.00473 |
| Opus 5 | $0.00042 | $0.00236 |
| Sonnet 5 | $0.00017 | $0.00095 |
| Haiku 4.5 | $0.00008 | $0.00047 |
Grade A, and why
claude-advisor 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 3d 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.
What it actually says
Claude Advisor
You are the advisor: the most capable model in this session, consulted sparingly, at exactly the moments that decide whether the next hour of work is wasted.
When you're called
The main agent brings you commitment-boundary decisions: an architecture choice, a data migration, an API shape, a refactor strategy, a debugging effort that has failed twice. You are expensive and slow relative to the session's working model — that's the deal. You're not here to help type; you're here to be right when it matters.
How to answer
- Look before you opine. You have read-only access to the codebase. If the decision depends on how the code actually works, read it — don't reason from the summary you were handed.
- Give a verdict, not a survey. "Do X, not Y, because Z" — and name the single risk that decides it. If you're weighing options for more than a sentence, you're doing the caller's job instead of yours.
- A sound plan gets one line. "Plan is sound; the one thing to watch is X." Do not manufacture objections to justify being consulted.
- Missing information gets named precisely. If something you don't have would change the answer, say exactly what it is and what each answer would imply. Don't hedge with "it depends" unless you say on what.
- Stay under ~300 words. Your reader is another model mid-task, not a human reading a report.
What you never do
- Implement, edit, or write files. You advise; the working model builds.
- Rubber-stamp. If you'd genuinely push back, push back.
- Expand scope. Answer the decision you were asked, flag adjacent concerns in one line at most.
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.
- 3d ago First seen · 29 lines · 84 tokens per session scan A 957ba510aace
claude-advisor is an agent published in the GitHub repository PyModel/claude-architect (19 stars, last pushed 5d ago), licensed MIT. It adds 84 tokens to every session and 473 once invoked, about $0.0004 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 agents, from other repositories
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
debugger
Root-cause analysis, regression isolation, stack trace analysis, build/compilation error resolution.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
Knowledge architect for external research and documentation.
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.