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/lgqyhm2010/loop-goal/agents-mdgit clone --depth 1 https://github.com/lgqyhm2010/loop-goalWrote 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/instructions/lgqyhm2010/loop-goal/agents-md)<a href="https://agentmods.dev/instructions/lgqyhm2010/loop-goal/agents-md"><img src="https://agentmods.dev/badge/instructions/lgqyhm2010/loop-goal/agents-md.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.00358 | $0.00358 |
| Opus 5 | $0.00179 | $0.00179 |
| Sonnet 5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
loop-goal 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 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.
What it actually says
AGENTS.md
This repository IS the loop-goal skill. When you (any agent) are about to run a
long-running task — one that repeats on an interval (a loop) or runs
until a completion criterion is met (a goal) — follow the loop-goal
discipline before you start.
Triggers: "loop", "goal", "keep running", "run in a loop", "until X", "run autonomously" — or the Chinese equivalents "持续做", "每隔", "循环跑", "直到…为止", "自主跑", "跑个 loop".
The six rules (summary):
- R1 — Init. Create
.loopgoal/state.jsonwith an explicitexit_condition. - R2 — Context isolation. Run each iteration/phase in a fresh subagent.
- R3 — Checkpoint order. Write state →
git commit→ then continue. - R4 — Resume. Read the state file and run
verify_cmdbefore each step. - R5 — Decision log. Append every tradeoff to
decisions[]. - R6 — Exit. Stop cleanly when
exit_conditionis met; never spin silently.
Full rules, checkpoint format, and loop/goal specifics:
skills/loop-goal/SKILL.md.
Copying this file into your own repo? Repoint the link above to wherever you
installed the skill (e.g. .agents/skills/loop-goal/SKILL.md), or drop it if you
rely on the skill's own auto-trigger.
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 · 27 lines · 358 tokens per session scan A ad92a4e0e7e9
loop-goal AGENTS.md is an instructions file published in the GitHub repository lgqyhm2010/loop-goal (10 stars, last pushed 2mo ago), licensed MIT. It adds 358 tokens to every session, about $0.0018 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).