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/fltman/loop-engineer/new-loopgit clone --depth 1 https://github.com/fltman/loop-engineerWhat 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.00013 | $0.00193 |
| Opus 5 | $0.00006 | $0.00097 |
| Sonnet 5 | $0.00003 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
new-loop 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 2d 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
Use the loop-architect agent to design and scaffold an agentic loop.
Goal: $ARGUMENTS
Rules:
- If the goal is empty, ask the user what "done" looks like.
- If the goal is not a binary, machine-checkable condition, your FIRST step is to convert it into one (or tell the user it isn't loop-ready) — do not scaffold a loop against a vague objective.
- Pick the pattern from the
loop-engineerskill's decision tree, scaffold the matching template, and wire all five guardrails (verifiable exit condition, max-iteration cap, in-code budget cap, sandbox, human checkpoint). - Hand off with: how to run it, how to stop it, and the per-iteration cost.
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.
- 2d ago First seen · 19 lines · 13 tokens per session scan A b22aa00f589e
new-loop is a command published in the GitHub repository fltman/loop-engineer (35 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 193 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-30.
Other commands, from other repositories
deploy
Deploy the following target to the specified environment.
review
Perform a comprehensive code review on the following target.
test
Execute a comprehensive test run for the following target.
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
preview
Open a URL in the desktop browser panel for the current session. With no argument it opens the workspace's static entry point, falling back to this session's existing preview target when no entry point exists. A local file can be opened by its absolute file:// URL. Use maestro preview clear to empty the panel.
doctor
Run local Maestro health checks. Use this to diagnose setup problems or verify the environment is correctly configured.