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/restarter/lets-workflow/opiniongit clone --depth 1 https://github.com/restarter/lets-workflowWhat 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.03935 |
| Opus 5 | $0.00006 | $0.01968 |
| Sonnet 5 | $0.00003 | $0.00787 |
| Haiku 4.5 | $0.00001 | $0.00394 |
Grade A, and why
opinion 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 2d 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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Decision Analysis
Analyze technical decisions by launching expert agents in parallel. Each agent provides their perspective, then results are aggregated into a clear recommendation.
DO NOT ask the user which option to choose. Analyze and recommend.
IMPORTANT: If the spec below invokes any deferred tool (e.g.
AskUserQuestion), you MUST load and call it as specified. Never skip the call, never substitute a default answer of your own — the tool invocation is part of the contract. This is critical.
Usage
/lets:opinion # Frame the decision interactively, then analyze
/lets:opinion <topic> # Analyze the given decision
/lets:opinion ... --workflow # Expert fan-out + adversarial challenge off-context via a Dynamic Workflow
Step 1: Frame the Problem
Parse the argument: strip a --workflow token if present (sets workflow mode); the rest is the topic. Mirror how /lets:plan strips --fast.
**Decision:** {what needs to be decided}
**Options:** A) ... B) ... C) ...
**Constraints:** {time, compatibility, legacy, budget}
Workflow execution flag
If --workflow is present, run the expert fan-out + challenge + synthesis inside a Dynamic Workflow instead of launching agents via the Task tool (Step 4 / 4.6 / 5 happen off-context; only the aggregate returns).
Choosing the execution path (interactive)
When --workflow was NOT explicitly passed:
- If the
Workflowtool is not available this session -> silently use the standard Task-based path. Do NOT show the option. - If the
Workflowtool is available -> ask viaAskUserQuestion:
AskUserQuestion(
questions=[{
question: "How should I run this analysis?",
header: "Run mode",
options: [
{ label: "Standard (Recommended)", description: "Experts via Task tool - full per-agent opinions visible inline" },
{ label: "Workflow", description: "Dynamic Workflow - off-context fan-out + challenge, only the recommendation returns" }
],
multiSelect: false
}]
)
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.
- 2d ago First seen · 374 lines · 13 tokens per session scan A 14ec2f4db961
opinion is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 9d ago), licensed MIT. It adds 13 tokens to every session and 3,935 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-30.
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.