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/Jaace/claude-model-advisorWrote 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/jaace/claude-model-advisor/model-check)<a href="https://agentmods.dev/commands/jaace/claude-model-advisor/model-check"><img src="https://agentmods.dev/badge/commands/jaace/claude-model-advisor/model-check/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/jaace/claude-model-advisor/model-check"><img src="https://agentmods.dev/badge/commands/jaace/claude-model-advisor/model-check.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.00000 | $0.00415 |
| Opus 5.5 | $0.00000 | $0.00166 |
| Sonnet 5.5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00042 |
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 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.
What it actually says
Reassess the current session and recommend the right model and effort level.
-
Briefly summarize what this session has been about so far (1-2 sentences).
-
Assess complexity on this scale:
- Simple: lookups, quick edits, factual Q&A, boilerplate
- Moderate: debugging, refactoring, multi-step coding tasks, explanations
- Complex: architecture decisions, hard reasoning, math, novel multi-system design
-
Choose model and effort independently — they are separate axes:
Model (what capability is needed?):
haiku— simple lookups, quick edits, boilerplate, straightforward factual questions; no effort levelsonnet— coding, debugging, refactoring, explanations, conceptual questions with some depthopus— novel architecture, hard math, genuinely ambiguous or open-ended design problems
Effort (how much reasoning is needed? — not applicable for Haiku; max is Opus only):
auto— Claude decides effort based on the task (default)low— the shape of the answer is already known; you are retrieving or explaining established knowledge, even if the topic is complexmedium— some reasoning or multi-step thinking required; the answer isn't immediately obvious but the path is clearhigh— genuinely hard reasoning required; the problem is ambiguous, involves hard tradeoffs with no clear answer, requires novel synthesis, or has many interdependent constraintsmax(Opus 4.6 only) — maximum thinking budget; use for the hardest problems where cost is no concern
-
Give a one-line rationale.
-
If a switch is warranted, tell the user to run
/modelto switch (up/down for model, left/right for effort). To adjust effort level only, they can run/effort [low|medium|high|max|auto].
No tools needed — pure reasoning and output only.
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 · 26 lines · 0 tokens per session scan A d2920df1f322
model-check is a command published in the GitHub repository Jaace/claude-model-advisor (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 415 tokens. 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 commands, from other repositories
model-config
Configure AI provider models for Claude Octopus workflows.
memory-shard-roll
Close finished calendar years out of an over-ceiling log-topic file (worklog/support/decisions) into a locked topic-YYYY.md shard, and update the parent's Shards index.
yapper-help
The /yapper-help command displays full documentation for the Yapper plugin, including all modes, commands, behaviours, configuration options, and usage examples. This command is itself rendered in Professor mode by default, because a help document that is not thoroughly elaborated would be somewhat contrary to the…
yapper-review
The /yapper-review command performs a thorough, multi-line pull request review. Rather than posting terse inline comments like "this is wrong" or "use X instead," yapper-review produces fully-explained feedback that describes the issue, the reasoning behind the concern, the potential impact, and a concrete suggested…
yapper-commit
The /yapper-commit command generates a verbose, fully-explained Git commit message for the current change or a described change. The resulting commit message explains not just what changed, but why it changed, what problem it solves, and how the solution works — providing maximum context for future readers of the git…
yapper
The /yapper command activates the Yapper verbosity system. Once active, all subsequent responses in the session will be substantially expanded, elaborated, and enriched with definitions, transitions, and restatements.