Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add restarter/lets-workflow/plugin install letsWrote 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/restarter/lets-workflow/research)<a href="https://agentmods.dev/commands/restarter/lets-workflow/research"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/research/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/restarter/lets-workflow/research"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/research.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.00030 | $0.03702 |
| Opus 5.5 | $0.00012 | $0.01481 |
| Sonnet 5.5 | $0.00006 | $0.00740 |
| Haiku 4.5 | $0.00003 | $0.00370 |
Grade A, and why
research 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 today.
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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research
Answer an external or technical question with a CITED synthesis: decompose the question, search + fetch the best sources, cross-check the claims to flag weak or contradicted ones, then present a sourced answer with a Sources list and an as-of date.
IMPORTANT: If the spec below invokes any deferred tool (e.g.
AskUserQuestion,WebSearch,WebFetch), 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.
When to use which
/lets:research |
/lets:opinion |
/lets:ask |
|
|---|---|---|---|
| Purpose | Sourced external answer | Project-grounded judgment / ideas | Quick model-knowledge consult |
| Output | Cited synthesis + Sources | Recommendation or insights | One expert's take |
| Input | A question (external facts) | A decision or open question about your project | A question |
| Grounding | Web sources (+ --project for repo) |
Your codebase via subagents, no web | Model knowledge |
Litmus: if the answer should end with a Sources list, it's research. Example: "which local LLM fits 32GB RAM + RTX 3080?" → research. "how should WE structure our rate-limiter?" → opinion (project-grounded, no sources).
Usage
/lets:research <question> # Research the question, return a cited synthesis
/lets:research # Ask what to research, then go
/lets:research <question> --workflow # Run research + cross-check off-context via a Dynamic Workflow
/lets:research <question> --project # Also ground findings against THIS repo (keeps the PROJECT_ROOT boundary)
Step 1: Parse + run mode
Parse the argument: strip a --workflow token (sets workflow mode) and a --project token (enables repo grounding) if present; the rest is the question.
If a question remains: use it. If not: ask via AskUserQuestion (header Research, question "What do you want me to research?") and wait.
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.
- today Changed eac14514a2d1
- 15d ago Changed · +2 lines c5df183e6e32
- 19d ago Changed · +2 lines 67eebe3e241a
- 20d ago Changed · +3 lines 452869e702ee
- 1mo ago Changed · +125 lines · +30 tokens per session 8b0dc60bf08b
- 1mo ago First seen · 71 lines · 0 tokens per session scan A f04b6c83c0f6
research is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 3,702 once invoked, about $0.0001 per session on Opus 5.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
audit-security
Check baseline CI security hygiene against the Starter Series bar — gitleaks, CodeQL, dep audit, license check, --ignore-scripts, Dependabot grouped, secret-scanning, claude-code-security-review, claude-security-guidance. Read-only, complementary to Anthropic's in-session security guidance plugin.
code-quality-plan-creator
LSP-powered architectural code quality analysis - works with any executor (loop or swarm).
mr-description-creator
Generate and apply MR/PR description directly via gh or glab CLI (project).
agy-review
Send the current change set to Antigravity (agy) for a senior-reviewer code review.
review
Two-stage code review (spec compliance + code quality).
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.