consult

consult is a command for Claude Code from yoichiojima-2/consultant. It costs 9 tokens per session (415 once invoked), scanned A, original, MIT.

A command that works through a business problem as a consulting engagement, from clarifying the question to presenting recommendations.

In plain words
What is it for?
It is for defining a problem, building an issue tree, prioritizing analysis, applying suitable business frameworks, and producing a final recommendation.
Why use it?
It gives a business investigation a defined sequence, making assumptions, priorities, evidence, and conclusions easier to follow.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the consulting plugin — 1 skill, 3 commands shipped together

Install

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.

agentmods
npx agentmods add commands/yoichiojima-2/consultant/consult
Clone the repo
git clone --depth 1 https://github.com/yoichiojima-2/consultant

Made for: Claude Code.

Or install consulting, the plugin that ships this one along with the rest of its 1 skill, 3 commands.

Wrote 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.

agentmods badge for consult

README.md
[![agentmods](https://agentmods.dev/badge/commands/yoichiojima-2/consultant/consult.svg)](https://agentmods.dev/commands/yoichiojima-2/consultant/consult)
Your own site
<a href="https://agentmods.dev/commands/yoichiojima-2/consultant/consult"><img src="https://agentmods.dev/badge/commands/yoichiojima-2/consultant/consult.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 415 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.00415
Opus 5 $0.00005 $0.00208
Sonnet 5 $0.00002 $0.00083
Haiku 4.5 $0.00001 $0.00042

Measured 6d ago against content hash 71829b87a5f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

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 6d 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.

commands/consult.md · 24 lines

What it actually says

Act as an engagement manager at a top consulting firm. Work the problem below through the complete consulting flow defined in the consulting skill (see ${CLAUDE_PLUGIN_ROOT}/skills/consulting/SKILL.md and the category files it references).

Problem: $ARGUMENTS

If no problem was provided above, ask for one and stop.

Follow this process, showing your work at each step:

  1. Clarify scope — Restate the problem. If critical context is missing (industry, timeframe, success criteria, constraints), ask up to 3 clarifying questions before proceeding. If the user gave enough context, state your assumptions explicitly and continue.
  2. Day-1 hypothesis — State your initial answer based on the situation as given.
  3. Define the problem (SCQ) — Situation, Complication, Question.
  4. Structure (Issue Tree) — Break the question into a MECE issue tree, 2–3 levels deep. Render it as an ASCII diagram.
  5. Prioritize (80/20) — Identify the 2–3 branches that likely drive most of the answer and say why you're deprioritizing the rest.
  6. Analyze — Work the priority branches. Select 1–3 frameworks from the skill that fit (e.g., Profitability, Porter's 5 Forces, Value Chain) — do not apply frameworks that don't earn their place. Quantify wherever possible; state assumptions for every number.
  7. Synthesize — For each analysis, extract the "So what?".
  8. Recommend (Pyramid Principle) — Lead with the answer in one sentence, then 3–5 supporting arguments with evidence, then risks and next steps.

End by offering to produce a deliverable from ${CLAUDE_PLUGIN_ROOT}/skills/consulting/templates/ (e.g., business case, SWOT report, project charter) if one fits.

Changes

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.

  1. 6d ago First seen · 24 lines · 9 tokens per session scan A 71829b87a5f4

Subscribe to this mod's changes

consult is a command published in the GitHub repository yoichiojima-2/consultant (41 stars, last pushed 16d ago), licensed MIT. It adds 9 tokens to every session and 415 once invoked, about $0.0000 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.