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/taberoajorge/loopforge/agents-mdgit clone --depth 1 https://github.com/taberoajorge/loopforgeWhat 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.01492 | $0.01492 |
| Opus 5 | $0.00746 | $0.00746 |
| Sonnet 5 | $0.00298 | $0.00298 |
| Haiku 4.5 | $0.00149 | $0.00149 |
Grade A, and why
loopforge 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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 144 lines · 1,492 tokens per session scan A b5061ea9733b
loopforge AGENTS.md is an instructions file published in the GitHub repository taberoajorge/loopforge (3 stars, last pushed 1mo ago), with no licence file. It adds 1,492 tokens to every session, about $0.0075 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-31.
Other instructions, from other repositories
claude-user-memory CLAUDE.md
Claude Code instructions for VAMFI/claude-user-memory, covering agentic substrate - advanced claude code enhancement, system version, 🔥 v4.1 key enhancements, deepwiki mcp integration (mandatory) and agent optimization.
warren AGENTS.md
Instructions for jayminwest/warren, covering agents.md, what this project is, runtime topology, the burrow absorption (plan pl-3007) and per-project config (.warren/config.yaml).
VisionClaw-Agent-Public-Release AGENTS.md
Instructions for Huskyauto/VisionClaw-Agent-Public-Release, covering agents.md — working in the visionclaw codebase, identity, the cardinal discipline: search before reading, hard rules (non-negotiable) and architecture map (entrypoints).
spine CLAUDE.md
Instructions for synaptixs/spine, covering spine — working on this repo, layout — where things live, invariants — break these and things get subtly wrong, gotchas that have bitten and before pushing.
factory CLAUDE.md
Instructions for watt-mind/factory: Claude, please refer to AGENTS.md and docs/protocol.md for the primary repository context, architecture, commands, operational rules, and tracker issue management standards.
swarm-357 CLAUDE.md
Instructions for TechTideOhio/swarm-357, covering claude.md, what this repo is, python package (packages/techtide-swarm/), or from pypi and key classes.