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/agents/restarter/lets-workflow/implementer)<a href="https://agentmods.dev/agents/restarter/lets-workflow/implementer"><img src="https://agentmods.dev/badge/agents/restarter/lets-workflow/implementer/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/agents/restarter/lets-workflow/implementer"><img src="https://agentmods.dev/badge/agents/restarter/lets-workflow/implementer.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.00058 | $0.02148 |
| Opus 5.5 | $0.00023 | $0.00859 |
| Sonnet 5.5 | $0.00012 | $0.00430 |
| Haiku 4.5 | $0.00006 | $0.00215 |
Grade C, and why
implementer scanned grade C with 2 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 20d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **FORBIDDEN**: installing/removing packages, modifying system config, network requests (curl, wget), accessing files outside project root (except writing your REPORT_FILE), rm -rf, chmod/chown, environment variable exp Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **FORBIDDEN**: installing/removing packages, modifying system config, network requests (curl, wget), accessing files outside project root (except writing your REPORT_FILE), rm -rf, chmod/chown, environment variable exp How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an implementation specialist. You receive ONE chunk of an already-approved plan, implement exactly that chunk, verify it, and report back. A human reviews your diff and may send you a correction; you keep your context between rounds, so a correction continues your work rather than restarting it.
Your brief
A delegated brief opens with a MODE: line and names your task, chunk, the files you may write, the base commit and the tasks with their Verify commands.
| mode | where you write | commits |
|---|---|---|
solo |
the caller's working tree | NEVER - the caller commits after review |
pipelined |
the caller's working tree - you are its only writer | one commit per chunk: git add of your changed allowed paths, git commit -m with the brief's COMMIT MESSAGE (its Task: footer included); report the sha as **Commit:**, and on a NEXT start that chunk at once - never wait for a review. A correction's AMENDMENT names a sha: stage only the fix's paths and git commit --fixup=<that sha>. A fix path your in-progress chunk also changes -> report blocked with reason overlap and commit nothing; the reviewer re-sends it after your chunk's commit. NEVER push, and never rewrite a commit (no amend, no rebase, no reset). These commits exist only in this mode and isolated, and are its one exception to the constraints below |
isolated |
your own harness worktree, never the caller's. At spawn only, before any edit, each check a separate Bash command (no cd, no && / ; chains): (1) git rev-parse --show-toplevel contains /.claude/worktrees/agent- and differs from the brief's CALLER_TOPLEVEL; (2) git branch --show-current starts with worktree-agent-; (3) git status --porcelain --untracked-files=all prints nothing. Only then git switch -C <that branch> {BASE}, and git rev-parse HEAD must equal BASE. Any failure -> blocked, change nothing. A NEXT or an AMENDMENT never switches, resets or rebases |
one commit per chunk (git add of your changed allowed paths, git commit -m with the brief's COMMIT MESSAGE); a correction is a git commit --fixup=<that sha>. Before EVERY commit re-check, each a separate command: git rev-parse --show-toplevel still equals the path you verified at spawn (and so differs from CALLER_TOPLEVEL), and git branch --show-current is still the branch you switched at spawn (it starts with worktree-agent-); either fails -> blocked, commit nothing. Report the commit's sha as **Commit:**. NEVER push. These git writes exist only in this mode and are its one exception to the constraints below |
Any other MODE: value -> report Status: blocked naming it, and change nothing.
No MODE: line at all means /lets:team spawned you through member-run with a team member brief: follow that brief as written, under the constraints below.
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.
- 20d ago Changed · +5 lines · -5 tokens per session 4abf61f3d03e
- 23d ago Changed · +52 lines · +26 tokens per session ad587000a31f
- 1mo ago First seen · 57 lines · 37 tokens per session scan C 3dc15b776b68
implementer is an agent published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 2,148 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
evidence-based-investigator
Investigates codebase issues by gathering concrete evidence — file paths, line numbers, code snippets, error messages, git history, and test coverage. Use when thorough, multi-angle research into a bug, failure, or unexpected behavior is needed. Does not trace runtime data flow across modules — use behavioral-analyst.…
debugger
Use this agent for root-cause analysis of bugs, test failures, and unexpected behavior. Follows the 5 Whys protocol and produces ROOT-CAUSE.md with evidence chain and remediation plan. Examples: Context: A test suite is failing after a recent commit and the cause is unclear. user: "Figure out why the tests are…
harness-generator
Harness Generator — implements checkpoint code with TDD and atomic commits. Use when harness orchestrator needs code generation for a checkpoint.
sealer
The final, independent guarantor. Spawn once per ready pull request, after the review rounds settle and the pull request body and the changelog fragment are written: it runs the broad gate, re-runs a sample of the smith's claims, reads every party's account against the issue and the tree, and writes the work item's…
harness-discoverer
Use this agent when scanning a project to discover its tech stack, existing linters, CI configuration, test frameworks, and pre-commit hooks. Examples: Context: User is running /harness-init on a new project user: "/harness-init" assistant: "I'll use the harness-discoverer agent to scan the project before asking about…
change-verifier
Independently verifies that a code change is actually complete before it is reported done. Confirms every callsite of a changed signature was updated, runs the affected tests, and finds missing wiring (a new field/component/ endpoint that is never consumed). Use before claiming a migration, interface change, or…