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/ronikobrosly/rigorloop/agents-mdgit clone --depth 1 https://github.com/ronikobrosly/RigorLoopWhat 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.01515 | $0.01515 |
| Opus 5 | $0.00758 | $0.00758 |
| Sonnet 5 | $0.00303 | $0.00303 |
| Haiku 4.5 | $0.00152 | $0.00152 |
Grade A, and why
RigorLoop 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Orientation for coding agents working in this repository. Read this first, then
read CODING_STYLE.md before writing or modifying any
code — its rules are hard constraints, not preferences.
What this package is
RigorLoop is a statistically-sound agentic loop-engineering framework. You give it a
task description, a pile of gold-standard input/output examples, and a set of
checks; it runs agentic loops (a strategy agent directing concurrent executor
agents) that iteratively build a solution and evaluate it on a strict
dev / validation / test split, so the final score is trustworthy. The
produced artifact is portable: an executable Python script, an agent skill
(SKILL.md), or a guidance file (AGENTS.md/CLAUDE.md).
- Pure Python, stdlib-only by design (no runtime dependencies), Python ≥ 3.12.
- Ships a single CLI:
rigorloop(init/check/run/report). - Invokes agents headless and tool-less via the
claudeCLI (claude -p). - User-facing docs:
README.md. Contributing:CONTRIBUTING.md.
Architecture: functional core / imperative shell
This is the single most important thing to understand, and it is enforced by
CODING_STYLE.md:
src/rigorloop/core/— the functional core. 100% pure: no I/O, no mutation, no time, no randomness, no network, no environment access. It decides; it returns values and plans of effects. Testable with plain inputs and zero mocks. Core coverage is held to a higher bar (≥95%).src/rigorloop/shell/— the thin imperative shell. Performs all effects (filesystem, subprocess, theclaudeCLI) and hands plain data to the core. Keep it small.
The dev/val/test split is encoded in the type system (DevExample,
ValExample, TestExample) so leaking holdout data into an agent-context
prompt is a type error, not a runtime bug. Don't defeat this.
Working in this repo
- Dev commands live in the
justfile, each mirroring a CI job:just lint,just typecheck,just test,just check(all three),just fmt. - Tooling:
uvfor env/build,ruff(lint + format),mypy --strict,pytest.T20(print) is banned in the core and allowed in the shell. - Every source module has a sibling test in
tests/(e.g.scoring_calcs.py→test_scoring_calcs.py);test_leakage.pyguards the split-type invariant andtest_e2e.pyruns full loops against fake agents.
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 · 122 lines · 1,515 tokens per session scan A 275598bc3a64
RigorLoop AGENTS.md is an instructions file published in the GitHub repository ronikobrosly/RigorLoop (77 stars, last pushed 1mo ago), licensed MIT. It adds 1,515 tokens to every session, about $0.0076 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-30.
Other instructions, from other repositories
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.
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).
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.
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).
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.