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/pealmeida/anymodel-plugin/review-withgit clone --depth 1 https://github.com/pealmeida/anymodel-pluginWrote 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/pealmeida/anymodel-plugin/review-with)<a href="https://agentmods.dev/commands/pealmeida/anymodel-plugin/review-with"><img src="https://agentmods.dev/badge/commands/pealmeida/anymodel-plugin/review-with.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 | $0.00013 | $0.00527 |
| Opus 5 | $0.00006 | $0.00264 |
| Sonnet 5 | $0.00003 | $0.00105 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
review-with 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
Run an adversarial review after helping the user choose the provider/model. This is the review-focused semantic chain for users who want a selected model to challenge the current implementation while the main CLI model orchestrates the command.
Raw user request:
$ARGUMENTS
Selection rules:
- If the request contains
--model <provider/model>, preserve it and skip model selection. - If it contains a natural model token such as
zai/glm-5.2,ollama/qwen3-coder, oropencode-go/kimi, convert that to--model <token>. - If it contains only a provider id, run:
Then ask the user to choose one reachable model returned for that provider.node "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" models --provider <provider> --json - If it contains no provider/model, run:
Then ask the user to choose from up to three reachablenode "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" models --json<provider>/<model>options. - Ignore providers where
okis false or no models are returned. - If no reachable model exists, return the models output verbatim and tell the user to run
/anymodel:setup.
Review rules:
- Preserve runtime and review flags exactly:
--engine,--base,--scope,--wait,--background,--cwd. - Preserve any focus text exactly after removing provider/model selector words.
- This command is review-only. Do not fix issues, apply patches, or suggest that you are about to make changes.
Foreground dispatch:
node "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" adversarial-review <final arguments>
Background dispatch:
- If the final arguments include
--background, launch the Bash command in the background and do not wait for completion. - Tell the user exactly: "AnyModel adversarial review started in the background. Check
/anymodel:statusfor progress."
Return foreground stdout verbatim. Do not summarize, fix, or add commentary after the review.
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 · 48 lines · 13 tokens per session scan A fe293a450dd2
review-with is a command published in the GitHub repository pealmeida/anymodel-plugin (0 stars, last pushed 26d ago), licensed Apache-2.0. It adds 13 tokens to every session and 527 once invoked, about $0.0001 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-31.
Other commands, from other repositories
/commit-push
Commit and push all changes from this chat session using Conventional Commits.
/release
Release a new version — updates CHANGELOG, pyproject.toml, creates git tag, and pushes.
mega-approve
Approve the mega-plan and start feature execution. Creates worktrees and generates PRDs for each feature. Usage: /plan-cascade:mega-approve [--flow ] [--tdd ] [--confirm] [--no-confirm] [--spec ] [--first-principles] [--max-questions N] [--auto-prd] [--agent ] [--prd-agent ] [--impl-agent ].
auto
AI auto strategy executor. Analyzes task and automatically selects and executes the best strategy: direct execution, hybrid-auto PRD generation, hybrid-worktree isolated development, or mega-plan multi-feature orchestration.
hybrid-auto
Generate PRD from task description and enter review mode. Auto-generates user stories with priorities, dependencies, and acceptance criteria for parallel execution. Usage: /plan-cascade:hybrid-auto [--flow ] [--tdd ] [--confirm] [--no-confirm] [--spec ] [--first-principles] [--max-questions N] [--agent ]…
hybrid-worktree
Start a new task in an isolated Git worktree with Hybrid Ralph PRD mode. Creates worktree, branch, loads existing PRD or auto-generates from description. Usage: /plan-cascade:hybrid-worktree [--flow ] [--tdd ] [--confirm] [--no-confirm] [--spec ] [--first-principles] [--max-questions N] [--agent ] [design-doc-path].