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.
npx agentmods add commands/madarauchiha-314/the-loop/stopgit 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/stop)<a href="https://agentmods.dev/commands/madarauchiha-314/the-loop/stop"><img src="https://agentmods.dev/badge/commands/madarauchiha-314/the-loop/stop.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 | $0.00000 | $0.00622 |
| Opus 5 | $0.00000 | $0.00311 |
| Sonnet 5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
stop 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 4d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
stop
Stop every running the-loop service — poller, webhook receiver, control-plane service — in reverse start order (issue-228, decision-084).
the-loop stop
stop deliberately ignores the enabled flags: a service you disabled after
starting it must still be stoppable. Each stop is the honest kind the daemons have had
since issue-159 — the pid is signalled only when the pidfile's lock proves a live
process holds it (never a stale pid that could belong to a stranger), and success is
reported only once the lock is released, so a scripted the-loop stop && the-loop start cannot overlap the shutdown it just asked for.
$ the-loop stop
poller stopped [enabled] stopped poller (pid 24913)
gh-webhook not-running [disabled] gh-webhook is not running
service stopped [enabled] stopped (pid 24846)
An ingress that is hosted inside the service
(issue-231) is stopped with it: stop recognises the lock is held by the service's
own pid, stops the one process, and reports success for the hosted rows only once
their locks are actually released.
$ the-loop stop
poller stopped [enabled] was hosted in the service (pid 24846); stopped with it
gh-webhook stopped [enabled] was hosted in the service (pid 24846); stopped with it
service stopped [enabled] stopped (pid 24846)
Standing sessions are stopped first, before the
ingresses and the service, so a session is taken down while the control plane it may be
talking to is still up — and every recorded one is stopped, whether or not
standingSessions.enabled still says so. Each keeps its record and its conversation id,
so the next start resumes rather than forgets.
$ the-loop stop
poller stopped [enabled] stopped poller (pid 24913)
gh-webhook not-running [disabled] gh-webhook is not running
service stopped [enabled] stopped (pid 24846)
standing sessions:
supervisor stopped stopped loop-standing-supervisor
Idempotent in both directions: stopping a stopped system exits 0 with not-running
rows. The exit code is non-zero only when something that was running failed to exit
within the timeout.
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.
- 4d ago First seen · 60 lines · 0 tokens per session scan A 04d59cefea28
stop is a command published in the GitHub repository MadaraUchiha-314/the-loop (4 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 622 tokens. 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
brainstorm
已弃用 - 请改用 superpowers:brainstorming 技能.
execute-plan
已弃用 - 请改用 superpowers:executing-plans 技能.
gaai-audit
Show workspace audit log with filters and optional JSON export.
gaai-ask
Search workspace memory — ranked entries with 1-hop graph context (cognitive guarantee).
gaai-update
Update the GAAI framework or switch AI tool adapter.
gaai-bootstrap
Initialize or refresh project context via Bootstrap Agent.