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/statusgit 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/status)<a href="https://agentmods.dev/commands/madarauchiha-314/the-loop/status"><img src="https://agentmods.dev/badge/commands/madarauchiha-314/the-loop/status.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.01081 |
| Opus 5 | $0.00000 | $0.00541 |
| Sonnet 5 | $0.00000 | $0.00216 |
| Haiku 4.5 | $0.00000 | $0.00108 |
Grade A, and why
status 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 yesterday.
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
status
One report for the whole system: per service, whether the config enables it, whether it is running (and as which pid), and the poller's progress (issue-228, decision-084).
the-loop status [--format text|json]
$ the-loop status
service running (pid 24846) [enabled] — http://127.0.0.1:4114, healthy
gh-webhook not running [disabled]
poller running (pid 24913) [enabled]
started: 2026-08-14T20:41:12Z (2m ago)
last cycle: 2026-08-14T20:43:02Z (10s ago) — 5 item(s), 1 spawn(s), 0 comment(s) forwarded
An ingress running inside the service
(issue-231) says so — same lock-based liveness, its lock is simply held by the
service's pid — and the JSON rows carry it as "hosted": true:
$ the-loop status
service running (pid 24846) [enabled] — http://127.0.0.1:4114, healthy
gh-webhook running (hosted in the service, pid 24846) [enabled]
poller running (hosted in the service, pid 24846) [enabled]
...
A repository the last cycle could not poll is named beneath that line, one degraded:
per repository, with the error and whether it is retried (issue-315,
decision-106). A repository whose Issues are disabled is skipped
for issues only and shows the standing reason; a cycle in which no repository answered
says so in words rather than leaving you to read it off 0 item(s):
$ the-loop status
poller running (pid 24913) [enabled]
started: 2026-09-02T20:41:12Z (3h ago)
last cycle: 2026-09-02T23:43:02Z (10s ago) — 24 item(s), 0 spawn(s), 1 comment(s) forwarded, 1 error(s)
degraded: octo/repo-b — listing failed, retried next cycle: gh issue list --repo exited 1: HTTP 502
degraded: octo/repo-m — issues are disabled on this repository; its issues are skipped and re-probed every 60 cycles, its pull requests are still polled
The exit code does not change for a degraded poller — it is running, and restarting it
would degrade identically; the lines are the signal. --format json carries the same
facts in the poller row's lastCycle (scopesPolled, scopesFailed, scopesSkipped).
Two properties carried over from the removed poll status (issue-191/205):
- Liveness and the pid come from the pidfile's lock, never from a file's claim. A
forged or leftover heartbeat cannot make a dead poller look alive, and a stale
pidfile is reported as not running — and left alone;
statusis read-only. - The heartbeat is enrichment. An absent or unreadable one loses the progress lines, never the liveness answer.
Standing sessions get their own section, and count
toward the exit code — but only the ones start would have
started (the block enabled, and the entry's autoStart true). One declared without
autoStart, or one that is only in the registry because you started it by hand, is
reported without deciding the answer.
$ the-loop status
service running (pid 24846) [enabled] — http://127.0.0.1:4114, healthy
...
standing sessions:
supervisor running [declared]
triage not running [declared, not auto-started]
The exit code is the health check (R3.3):
0 iff every enabled service is running, so the-loop status || … is the keepalive
primitive. --format json emits the same facts as one document (per-service rows plus
ok), including the service's URL, its /health answer, whether /mcp is exposed,
and the poller's last-cycle counters.
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.
- yesterday Changed · +19 lines a47a448e861d
- 5d ago First seen · 66 lines · 0 tokens per session scan A fd5527fddc51
status is a command published in the GitHub repository MadaraUchiha-314/the-loop (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,081 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
receipts
Find the receipt. A dated line, or it did not happen.
ship
Seen on their staging, then live. Rollback you have run.
negative-keyword-sweep
Find wasted spend in Google Ads search terms and add negatives at the right scope (account list, campaign, or ad group). Use when the user says "find junk keywords", "stop wasting on bad searches", or wants a search-terms cleanup.
import
Import a shared context bundle, or take a teammate's newer copy of one you already have.
duck-off
Turn off Rubber Duck mode and answer normally.
extensions
Show what the connected context expects to reach, and whether this machine provides it.