Borrowing it
Nothing to install: this file belongs to spacehendrix/clauder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/spacehendrix/clauder/main/.claude/commands/consult.mdgit clone --depth 1 https://github.com/spacehendrix/clauderWrote 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/spacehendrix/clauder/consult)<a href="https://agentmods.dev/commands/spacehendrix/clauder/consult"><img src="https://agentmods.dev/badge/commands/spacehendrix/clauder/consult/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/spacehendrix/clauder/consult"><img src="https://agentmods.dev/badge/commands/spacehendrix/clauder/consult.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.00107 |
| Opus 5.5 | $0.00000 | $0.00043 |
| Sonnet 5.5 | $0.00000 | $0.00021 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
consult 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 12d 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
Consult "openai/gpt-6.1-sol", or otherwise specified model, through OpenRouter (must be setup and authenticated)
Use the "consult7" MCP server to request help from "openai/gpt-6.1-sol", or the model explicitly specified, regarding the following request.
Send it the following request, along with the relevant codebase, ALWAYS EXCLUDING all files and folders described in .claudeignore and .gitignore, as well as any file for which the name includes .env
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.
- 12d ago Changed bb20ade419b8
- 1mo ago First seen · 4 lines · 0 tokens per session scan A f22d276a3e2f
consult is a command published in the GitHub repository spacehendrix/clauder (58 stars, last pushed 12d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 107 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-09-03.
Other commands, from other repositories
amby.revise
Continue an existing feature's spec (or design) — add and refine in place, with a done-guard.
amby.converge
Check the codebase against spec, plan, and tasks after implementing; append gap tasks, never edit code.
amby.design
Design the UI — wireframes, component specs, and design tokens — with a sign-off gate.
amby.implement
Execute the task list, checking off tasks and updating story status as you go.
amby.plan
Produce the technical implementation plan (the HOW) from an approved spec and UI.
amby.analyze
Cross-check spec, plan, and tasks for coverage, consistency, and dependency-graph health.