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 instructions/eldergenix/proofloop/agents-mdgit clone --depth 1 https://github.com/Eldergenix/ProofloopWhat 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.00665 | $0.00665 |
| Opus 5 | $0.00332 | $0.00332 |
| Sonnet 5 | $0.00133 | $0.00133 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
Proofloop AGENTS.md 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.
This is a copy
100% identical to loop AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Please keep the code dead-simple and keep the src/loop/main.ts file under 150 lines of code.
Quick Commands
- Format code:
bun run fix - Check lint/types/style:
bun run check - Run tests:
bun test - Build executable:
bun run build - Install global binary/aliases:
bun run install:global - Cut a patch release:
bun run release:patch
Repo Workflows
- Plain-text prompts auto-create
PLAN.mdfirst, then optionally run--review-plan; if you are changing planning behavior, keep that flow aligned. - Default CLI behavior is paired Claude/Codex execution with persisted run state under
~/.loop/runs; preserve--run-id/--sessionresume behavior when changing startup, planning, or loop flow. - Running
loopwith no args starts the paired interactive tmux workspace (--tmux);loop dashboardopens the live panel for active sessions, loop-owned paired runs, and tmux sessions. Keep panel-only changes separate from task-running changes when possible. --tmuxand--worktreeare first-class execution modes. In paired mode, tmux opens Claude/Codex side-by-side and resumed run ids should stay aligned with matching tmux/worktree names.--claude-onlyand--codex-onlyswitch out of the default paired flow; keep single-agent behavior working when changing shared CLI parsing or resume logic.loop update/loop upgradeare supported manual update commands for installed binaries; source runs should continue to rely ongit pull.- When options are provided without a prompt,
loopreusesPLAN.mdif it already exists; keep that fallback aligned with the plain-text prompt planning flow.
Coding Standards
- Keep functions small and easy to read.
- Use explicit parameter/return types when they improve clarity.
- Prefer
unknownoveranyfor unknown values. - Use
constby default,letonly when reassignment is needed. - Prefer
for...of, optional chaining, nullish coalescing, and template literals. - Use early returns to reduce nesting.
- Use
async/awaitinstead of promise chains. - Throw
Errorobjects with clear messages. - Extract magic numbers/strings into named constants when reused.
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 · 53 lines · 665 tokens per session scan A d3ac41c45b52
Proofloop AGENTS.md is an instructions file published in the GitHub repository Eldergenix/Proofloop (41 stars, last pushed 3mo ago), licensed MIT. It adds 665 tokens to every session, about $0.0033 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to loop AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
calc-mcp CLAUDE.md
Instructions for coo-quack/calc-mcp, covering project rules, tech stack, commands, project structure and tool architecture.
get-fable AGENTS.md
Instructions for imMamdouhaboammar/get-fable, covering get-fable repository instructions, purpose, working contract, canonical lifecycle packs and runtime semantics.
umbel CLAUDE.md
Instructions for jahala/umbel, covering umbel — project guidelines for claude code, what this is, non-negotiable principles, architecture layers (strict downward dependency) and stack.
plugin.delivery AGENTS.md
AGENTS.md instructions for nirholas/plugin.delivery, covering plugin.delivery development guidelines, project overview, terminal management and contributing.
plugin.delivery copilot-instructions.md
Copilot instructions for nirholas/plugin.delivery, covering plugin.delivery and terminal management.
plugin.delivery CLAUDE.md
Claude Code instructions for nirholas/plugin.delivery, covering plugin.delivery and terminal management.