start

start is a command for coding agents from MadaraUchiha-314/the-loop. It costs 0 tokens per session (1,202 once invoked), scanned A, original, MIT.

A command that reads the-loop's CLI configuration and starts every enabled service in the background.

In plain words
What is it for?
Use it to start the control plane, dashboard, MCP endpoint, webhook receiver, poller, or standing sessions according to configuration.
Why use it?
It brings the configured system up in one step and reports whether each service started, was disabled, or failed. It does not start optional services unless they are enabled.

Command

Part of the the-loop plugin — 2 skills, 35 commands, 2 hooks shipped together

Install

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.

agentmods
npx agentmods add commands/madarauchiha-314/the-loop/start
Clone the repo
git clone --depth 1 https://github.com/MadaraUchiha-314/the-loop

Or install the-loop, the plugin that ships this one along with the rest of its 2 skills, 35 commands, 2 hooks.

Wrote 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.

agentmods badge for start

README.md
[![agentmods](https://agentmods.dev/badge/commands/madarauchiha-314/the-loop/start.svg)](https://agentmods.dev/commands/madarauchiha-314/the-loop/start)
Your own site
<a href="https://agentmods.dev/commands/madarauchiha-314/the-loop/start"><img src="https://agentmods.dev/badge/commands/madarauchiha-314/the-loop/start.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,202 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01202
Opus 5 $0.00000 $0.00601
Sonnet 5 $0.00000 $0.00240
Haiku 4.5 $0.00000 $0.00120

Measured 4d ago against content hash f59ce658199d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

start 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.

docs/cli/commands/start.md · 99 lines

How it starts

The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.

start

Bring the-loop up: one command that reads the CLI config and starts, detached, every service it enables (issue-228, decision-084).

the-loop start
Service Enabled by Default
Control-plane service (REST + dashboard) service.enabled on
MCP endpoint (/mcp, mounted on the service) service.mcp.enabled on
GitHub webhook receiver webhooks.ghWebhook.enabled off
Poller polling.enabled off
Standing sessions standingSessions.enabled off

The ingresses are explicit opt-ins: a config that merely describes a receiver or a polling source must not open a port or start a loop. start prints one line per service — started, hosted (see below), already-running (start is idempotent), disabled (naming the key that enables it), misconfigured (an enabled poller with no polling.sources), or failed (pointing at the service's logfile) — and exits 0 only when every enabled service came up. One service failing never hides the others' outcomes.

One process by default

With the service enabled and service.hostIngresses at its default (true, issue-231), start boots one process: the service, which runs the enabled ingresses as background threads inside its own lifespan. Each hosted ingress still holds its own pidfile lock — under the service's pid — so status, stop and the daemons API answer unchanged, and an ingress already running standalone is skipped with a warning, never fought over.

$ the-loop start
service     started          [enabled]  started at http://127.0.0.1:4114; /mcp exposed
gh-webhook  hosted           [enabled]  in the service process (pid 24846)
poller      hosted           [enabled]  in the service process (pid 24846)

Read the full file on GitHub · 99 lines

Changes

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.

  1. 4d ago First seen · 99 lines · 0 tokens per session scan A f59ce658199d

Subscribe to this mod's changes

start 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 1,202 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.