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.
git clone --depth 1 https://github.com/restarter/lets-workflowWrote 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/plugins/restarter/lets-workflow/lets)<a href="https://agentmods.dev/plugins/restarter/lets-workflow/lets"><img src="https://agentmods.dev/badge/plugins/restarter/lets-workflow/lets/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/plugins/restarter/lets-workflow/lets"><img src="https://agentmods.dev/badge/plugins/restarter/lets-workflow/lets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lets 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.
What it actually says
{
"name": "lets",
"description": "Development workflow with session management, code review, and task tracking",
"version": "0.11.0",
"author": {
"name": "restarter",
"url": "https://github.com/restarter"
},
"license": "MIT",
"homepage": "https://github.com/restarter/lets-workflow",
"repository": "https://github.com/restarter/lets-workflow",
"keywords": [
"workflow",
"review",
"sessions",
"beads",
"code-review",
"task-tracking"
]
}
What it installs
The manifest is a name and a version. 20 skills, 26 commands, 16 agents travel with it, and installing the plugin installs all of them — 2,906 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill detect-task A 41 tokens
- Skill orc A 171 tokens
- Skill take-task A 76 tokens
- Skill agent-report A 54 tokens
- Skill commit A 96 tokens
- Skill create-task A 79 tokens
- Skill member-run A 84 tokens
- Skill plan-workflow A 51 tokens
- Skill session-boundary A 55 tokens
- Skill apply-fixes A 63 tokens
- Skill orient A 42 tokens
- Skill protocol-tracker A 62 tokens
- Skill research-workflow A 54 tokens
- Skill review-workflow A 56 tokens
- Skill artifact-path A 63 tokens
- Skill backlog-workflow A 51 tokens
- Skill opinion-workflow A 57 tokens
- Skill protocol-orchestrator-offer A 73 tokens
- Skill actor-fetch-personality A 37 tokens
- Skill session-snapshot B 82 tokens
- Command review A 30 tokens
- Command done A 12 tokens
- Command team A 19 tokens
- Command worktree A 16 tokens
- Command handoff A 116 tokens
- Command plan A 17 tokens
- Command start A 12 tokens
- Command backlog A 23 tokens
- Command check A 17 tokens
- Command end A 63 tokens
- Command opinion A 13 tokens
- Command plan-workflow A 38 tokens
- Command research A 30 tokens
- Command note A 54 tokens
- Command ask A 15 tokens
- Command review-round A 66 tokens
- Command hub A 30 tokens
- Command statusline A 18 tokens
- Command status A 20 tokens
- Command peer A 19 tokens
- Command review-handoff A 42 tokens
- Command execute C 27 tokens
- Command github-pr C 20 tokens
- Command init C 35 tokens
- Command update C 69 tokens
- Command install-deprecated C 13 tokens
- Agent skeptic A 92 tokens
- Agent docs A 38 tokens
- Agent pragmatist A 53 tokens
- Agent actor A 37 tokens
- Agent architect A 39 tokens
- Agent backend A 39 tokens
- Agent compliance A 40 tokens
- Agent database A 37 tokens
- Agent devops A 48 tokens
- Agent explorer A 35 tokens
- Agent frontend A 39 tokens
- Agent git-historian A 46 tokens
- Agent qa A 40 tokens
- Agent security A 39 tokens
- Agent lead A 45 tokens
- Agent implementer C 58 tokens
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 Changed 0ef208645c14
- 20d ago Changed f11df0abea30
- 22d ago Changed 93ffed71ae5d
- 23d ago Changed f6b8fb65baee
- 28d ago Changed feb399708287
- 1mo ago Changed 9ceaea1c04a2
- 1mo ago Changed dec26a0e444a
- 1mo ago First seen · 21 lines scan A fe4dc6e98999
lets is a plugin published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
han-linear
Linear-facing extensions to the Han suite. Adds work-items-to-linear, which creates one Linear issue per slice from a work-items file. Works through the Linear MCP server and requires it to be configured. Depends on no other Han plugin. Opt-in: installed on its own, not pulled in by the han meta-plugin.
claudelint
A comprehensive linter for Claude Code projects. Validates CLAUDE.md files, skills, settings, hooks, MCP servers, plugins, and more. Requires: npm install --save-dev claude-code-lint.
pm
GitHub issue lifecycle: brainstorm design approaches, create structured issues for LLM agent teams, triage and recommend next issues, audit and clean up stale backlogs, and deep-validate individual issues against the codebase.
fullstack-dev-kit
Issue-to-PR workflow kit for any tech stack. Fetch a user story from your tracker (Jira, Linear, GitHub Issues, Azure DevOps) and any linked Figma designs, implement with plan approval, enforce >95% coverage and a security pass, generate e2e tests, open the PR, fix review findings, and move the ticket to review.
linear-workspace
Linear issue management for Claude Code — search, bulk operations, intelligent agents, config-driven curator. Backed by the elnora-linear CLI.
stereo
Pair Claude with the Codex CLI: mixed-model planning and implementation, adversarial reviews, delegated tasks, and background jobs.