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/ciroaurelio22/agentloop/agents-mdgit clone --depth 1 https://github.com/ciroaurelio22/AgentLoopWhat 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.00421 | $0.00421 |
| Opus 5 | $0.00211 | $0.00211 |
| Sonnet 5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
AgentLoop 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.
What it actually says
Agent Loop — instructions for coding agents
This file applies to any agent working in this repository (Cursor, Claude Code, Codex, etc.).
Before every push
You must bump the root VERSION file before pushing to GitHub.
The kit uses VERSION as the release identifier: installs copy it to .agent-loop/kit-version, and agent-update-check compares it with the remote file on GitHub.
How to bump
- Read the current value in
VERSION(single line, semver, e.g.0.1.0). - Increment it before
git push:- Patch (
0.1.0→0.1.1): default for bug fixes, GUI tweaks, docs, and most kit changes. - Minor (
0.1.0→0.2.0): new features or behavior changes that are backward compatible. - Major (
0.1.0→1.0.0): breaking changes to install layout, CLI contract, or queue/task format.
- Patch (
- Write only the new version string in
VERSION(novprefix, no extra lines). - Include
VERSIONin the same commit you push, or in a dedicated release commit immediately before push.
Do not push without a version bump
If the branch has user-facing or kit changes that will land on master, do not push until VERSION is updated. Skipping this breaks update notifications for downstream repos.
Quick checklist
- Changes committed
-
VERSIONincremented -
git push(only when the user asked to push)
Related docs
README.md— install, workflow, backendsadapters/cursor/skills/update/SKILL.md— update flow and Agent Console restart
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 · 35 lines · 421 tokens per session scan A 63fc8ebdd2be
AgentLoop AGENTS.md is an instructions file published in the GitHub repository ciroaurelio22/AgentLoop (10 stars, last pushed 2mo ago), licensed MIT. It adds 421 tokens to every session, about $0.0021 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
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.
buildNext
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
spec-kit 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
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.