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/installgit 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/install)<a href="https://agentmods.dev/commands/madarauchiha-314/the-loop/install"><img src="https://agentmods.dev/badge/commands/madarauchiha-314/the-loop/install.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.01793 |
| Opus 5 | $0.00000 | $0.00897 |
| Sonnet 5 | $0.00000 | $0.00359 |
| Haiku 4.5 | $0.00000 | $0.00179 |
Grade B, and why
install scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`<config dir>/settings.json` (user scope) or `<project>/.claude/settings.json` (project How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
install
Put the-loop on a machine: the CLI and the Claude Code plugin, at user or project scope.
the-loop install [COMPONENT ...] [--scope user|project] [--project-dir .]
[--from owner/repo] [--dry-run] [--format table|json]
$ the-loop install --dry-run
the-loop install · components: cli, claude · scope: user · marketplace: MadaraUchiha-314/the-loop · dry run
Component Outcome Step Command / file
--------- ------- ---------------------------------------------- --------------------------------------------------------
cli planned install the the-loopy-one CLI /usr/bin/uv tool install the-loopy-one
claude planned register the the-loop marketplace (…/the-loop) claude plugin marketplace add MadaraUchiha-314/the-loop …
claude planned install the-loop@the-loop claude plugin install the-loop@the-loop --scope user
Components are cli, claude, or all. Naming none means the CLI plus every
harness actually found on PATH — the useful default when setting a machine up.
Cursor is not a component yet. the-loop ships as a Cursor plugin (decision-015), but installing it from a terminal is its own problem — as of Cursor 2.5 the documented routes are the marketplace site and
/add-pluginin the editor, and no CLI install command appears to be documented. Tracked as issue #157; until then, install the Cursor plugin the way the installation guide describes.This installs software. Scaffolding a repository is
/the-loop:init, and reconciling a project's the-loop files with a newer plugin is/the-loop:upgrade-the-loop. Different jobs, deliberately different commands.
It plans, then executes
Every run builds an ordered plan of steps and prints the exact argv (or the file path) of
each one, then executes it. --dry-run is the same plan with the execution left out —
not a separate code path that could drift from the real one — so a preview shows the
skips too.
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 · 150 lines · 0 tokens per session scan B 0e75b2388cb5
install 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,793 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.