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/shalomeir/advisor-opus/plangit clone --depth 1 https://github.com/shalomeir/advisor-opusWrote 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/shalomeir/advisor-opus/plan)<a href="https://agentmods.dev/commands/shalomeir/advisor-opus/plan"><img src="https://agentmods.dev/badge/commands/shalomeir/advisor-opus/plan.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.00064 | $0.00686 |
| Opus 5 | $0.00032 | $0.00343 |
| Sonnet 5 | $0.00013 | $0.00137 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
plan 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Route this request to the advisor-opus:opus-advisor subagent with a planning-specific framing.
IMPORTANT: The advisor agent starts fresh with NO conversation history. You (the executor) must build the context.
Raw user request: $ARGUMENTS
Context Gathering (executor does this BEFORE spawning the advisor)
The advisor starts with zero context — it cannot see your conversation at all. You must pass it everything it needs. Follow these three steps in order:
Step 1 — Task summary (1-2 sentences): Write what the user wants to build, change, or fix. Example: "User wants to migrate the REST API from Express to Hono."
Step 2 — What you know (bullet list, keep short): List codebase structure, relevant files, technologies, constraints. Include key file paths. Compress old findings into short bullets.
Step 3 — Recent raw output (copy-paste, do NOT summarize): Copy the last 3-5 tool results exactly as they appeared — file contents, grep results, exploration findings. The advisor needs the actual text to plan accurately. If a tool returned 50 lines, include all 50 lines.
Optional: run git diff --stat and git status to show current state.
Structure the advisor prompt as:
## Task
[1-2 sentence summary of what needs to be planned]
## Codebase Context
- [key files, structure, technologies]
- [constraints, dependencies discovered]
- [what has been explored so far]
## Recent Context (verbatim)
[last 3-5 tool calls/results — file reads, grep results, etc.]
## Planning Request
[user's $ARGUMENTS]
Routing Rules
-
If
$ARGUMENTSis empty, ask the user what they want to plan. -
Build the context as described above.
-
Forward to the
advisor-opus:opus-advisorsubagent with the structured context, plus this prefix:"Create a strategic implementation plan for the following task. This is a planning task — provide a comprehensive, detailed plan without the usual 100-word limit. Structure your response as:
- End State — what 'done' looks like
- Critical Path — ordered steps with dependencies
- Risks — what could go wrong and how to mitigate
- First Move — the single best action to start with"
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.
- 5d ago First seen · 65 lines · 64 tokens per session scan A 43f92cc13282
plan is a command published in the GitHub repository shalomeir/advisor-opus (10 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 686 once invoked, about $0.0003 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.