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/MadaraUchiha-314/the-loopWrote 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/madarauchiha-314/the-loop/finish-tasks)<a href="https://agentmods.dev/commands/madarauchiha-314/the-loop/finish-tasks"><img src="https://agentmods.dev/badge/commands/madarauchiha-314/the-loop/finish-tasks.svg" alt="Measured on agentmods" 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.00023 | $0.00435 |
| Opus 5 | $0.00012 | $0.00217 |
| Sonnet 5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
finish-tasks 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 8d 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
the-loop: finish-tasks $ARGUMENTS
Wrap up a work item once all tasks are complete and reviewed. This is the cleanup step of the loop; the cleanup set is intentionally extensible (more may be added later).
Read the the-loop skill and reference/workflow.md. Load .the-loop/harness-config.yaml.
Steps
-
Verify done. Resolve
$ARGUMENTStodocs/specs/<id>/. Confirm every task intasks.mdis checked (- [x]), every PR in the execution log's Pull requests table is merged or closed (a work item may be delivered by several), the required self/critic reviews and human review are recorded, and validated evidence has been presented. If anything is outstanding, stop and report what remains (point back to/the-loop:execute-tasks <id>). -
Mark complete. Set the ticket phase label to
<phaseLabelPrefix>completeand mirrorphase: completein the spec/execution log; add a final execution-log entry summarizing outcome + evidence. -
Cleanup (extensible):
- Close the ticket(s) for this work item (GitHub issue / Jira), referencing the
merged PR(s) / evidence. Closing the ticket is also what ends the work item's
harness session — one of its PRs merging does not (see
reference/automation.md). - Future cleanup steps are added here (e.g. archiving branches, releasing artifacts, notifying channels). Keep this list the single place cleanup grows.
- Close the ticket(s) for this work item (GitHub issue / Jira), referencing the
merged PR(s) / evidence. Closing the ticket is also what ends the work item's
harness session — one of its PRs merging does not (see
-
Report the final status and links.
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.
- 8d ago First seen · 35 lines · 23 tokens per session scan A 8b9ff5c13a80
finish-tasks is a command published in the GitHub repository MadaraUchiha-314/the-loop (4 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 435 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-31.
Other commands, from other repositories
close
They operate it without you.
estimate-work
Estimate a task or project honestly, by decomposing it, surfacing unknowns, and giving a range not a false point.
meeting-request-email
Write an email requesting a meeting that states the purpose, respects their time, and makes scheduling easy.
pre-mortem
Run a pre-mortem: imagine the project already failed, work backward to the causes, and prevent them now.
promotion-packet
Write a promotion packet or self-review that frames your work as impact at the next level, with evidence.
burndown-full
Drive a partially-executed plan to 100% coverage across the whole repo — enumerate, batch-execute, prove completeness.