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/ask)<a href="https://agentmods.dev/commands/restarter/lets-workflow/ask"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/ask/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/ask"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/ask.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.00015 | $0.01506 |
| Opus 5.5 | $0.00006 | $0.00602 |
| Sonnet 5.5 | $0.00003 | $0.00301 |
| Haiku 4.5 | $0.00002 | $0.00151 |
Grade A, and why
ask 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 19d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask an Expert
Quick consultation with a single expert agent. Like pinging a colleague on Slack.
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:ask # Interactive - asks who and what
/lets:ask security "is this safe?" # Direct to expert with question
/lets:ask architect # Opens dialog, asks question after
Difference from /lets:opinion
| /lets:ask | /lets:opinion | |
|---|---|---|
| Purpose | Ask one colleague | Team meeting |
| Experts | Always 1 | Dynamic, in parallel |
| Input | Question | Decision + options |
| Output | Direct answer | Comparison table + recommendation |
| Analogy | Slack ping | 30 min meeting |
Step 1: Determine Expert
If specified in arguments - use it. Otherwise use AskUserQuestion to pick.
Available experts (map to lets:* agents):
| # | Shorthand | Agent (subagent_type) | Expertise |
|---|---|---|---|
| 1 | architect | lets:architect | System design, patterns, SOLID |
| 2 | security | lets:security | Vulnerabilities, auth, crypto |
| 3 | backend | lets:backend | API, logic, performance |
| 4 | frontend | lets:frontend | UI, React/Vue, a11y |
| 5 | database | lets:database | Schema, queries, migrations |
| 6 | devops | lets:devops | Docker, CI/CD, infrastructure |
| 7 | qa | lets:qa | Testing, coverage, strategy |
| 8 | docs | lets:docs | Documentation, API docs |
| 9 | compliance | lets:compliance | Project rules, standards |
| 10 | git-historian | lets:git-historian | History, past decisions, blame |
| 11 | pragmatist | lets:pragmatist | ROI, effort vs value, scope |
| 12 | actor | lets:actor | External personality - any expertise via loaded persona |
Shorthand mapping: User can type short names like "security" or "sec" - map to the correct agent subagent_type.
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.
- 19d ago Changed · +4 lines 640151ec3674
- 20d ago Changed · +3 lines cd55c89b175f
- 1mo ago First seen · 154 lines · 15 tokens per session scan A a3c6fb3466c3
ask is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 1,506 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
todo
The quality-gated task list: tasks with real descriptions, testable acceptance criteria, and evidence — a task only closes when the controller agrees it is done.
develop
Implement skill development issues with TDD-governed workflow.
release-flow
Portable gated release flow — deterministic gate + vendor-agnostic independent reviewer, runnable from any harness.
triage-inbox
Sort application mail into the freehire tracker and drain the link queues.
retro
Score zforge's workflow performance on a feature.
audit-release
Diagnose release-readiness against the Starter Series quality bar — matched starter, version-vs-last-tag drift, CHANGELOG drift vs merged PRs, and publish-workflow kind. Read-only.