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/instructionsgit 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/instructions)<a href="https://agentmods.dev/commands/madarauchiha-314/the-loop/instructions"><img src="https://agentmods.dev/badge/commands/madarauchiha-314/the-loop/instructions.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.00989 |
| Opus 5 | $0.00000 | $0.00495 |
| Sonnet 5 | $0.00000 | $0.00198 |
| Haiku 4.5 | $0.00000 | $0.00099 |
Grade A, and why
instructions 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 5d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
instructions
Which of the custom instruction docs your project registers actually resolve — so
"is the-loop really reading my conventions?" is a question you can answer, and
onMissing: error is a setting that errors.
the-loop instructions [--root .] [--format table|markdown|json]
What it reads
customInstructions.docs in the repository's
harness config — the ordered list of your own rule and
guideline files the loop reads before working an item
(instructions reference):
customInstructions:
docs: # ordered; later docs win on conflict
- path: docs/team-conventions.md # repo-relative …
notes: House TS style, naming, PR etiquette.
- path: /home/me/company-wide-rules.md # … or absolute (per-machine)
notes: Org-wide security & dependency policy.
onMissing: warn # warn | error | ignore
It reports each entry in configured order — order matters, because later docs win on
conflict — with its configured path, the absolute path it resolved to, your notes, and
its state.
States
| State | Meaning |
|---|---|
present |
The file is there and readable. Its guidance reaches the agent. |
missing |
Nothing resolves at that path (including a broken symlink). Usually a typo or a moved file. |
unreadable |
Something is there, but it is not a readable text file — a directory, a device node, an unpermitted file, or binary content. |
invalid |
The entry itself is unusable: no path, a blank one, or not a mapping. |
missing and unreadable are kept apart on purpose: "your path is wrong" and "your path
is right but the target is not a doc" send you to different places.
Exit code
Everything that is not present counts as unresolved — invalid included, because a
registration the-loop could not understand is guidance that is not reaching the agent.
What happens then is customInstructions.onMissing:
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.
- 5d ago First seen · 98 lines · 0 tokens per session scan A 7f110f8a22f4
instructions 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 989 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.