loop-designer: Instructions file for Codex

AGENTS.md

loop-designer AGENTS.md is an instructions file for Codex, OpenCode from groktopus/loop-designer. It costs 336 tokens per session, scanned A, original, MIT.

A set of instructions for designing autonomous agent loops: repeated runs that pursue a goal, check results, remember state, and stop safely.

In plain words
What is it for?
Set up goal judging, verification agents, scheduled runs, task dependencies, memory, restricted tools, and limits on repeated attempts.
Why use it?
It gives a repeatable structure for long-running work instead of relying on one agent run to finish everything correctly.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions subagents.

This is groktopus/loop-designer's own configuration. It tells Codex and OpenCode how to work on loop-designer itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything loop-designer configures →

Reuse

Borrowing it

Nothing to install: this file belongs to groktopus/loop-designer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/groktopus/loop-designer/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/groktopus/loop-designer

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for loop-designer AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/groktopus/loop-designer/agents-md/github.svg)](https://agentmods.dev/instructions/groktopus/loop-designer/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/groktopus/loop-designer/agents-md"><img src="https://agentmods.dev/badge/instructions/groktopus/loop-designer/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for loop-designer AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/groktopus/loop-designer/agents-md"><img src="https://agentmods.dev/badge/instructions/groktopus/loop-designer/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 336 This file is loaded in full into every session.
When invoked 336 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00336 $0.00336
Opus 5.5 $0.00134 $0.00134
Sonnet 5.5 $0.00067 $0.00067
Haiku 4.5 $0.00034 $0.00034

Measured 2mo ago against content hash 94a649d85ce9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

loop-designer 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 2mo 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.

AGENTS.md · 34 lines

What it actually says

loop-designer

Autonomous agent loop design in 10 steps. See SKILL.md for full methodology.

This skill distills Alex (@de1lymoon)'s 10-step roadmap into concrete Hermes Agent invocations — from /goal with goal_judge to unattended cron loops with memory, verification, and fail-safe guardrails.

Quick Reference

Step Article Move Hermes Mechanism
1 Agent is a loop /goal loops via goal_judge
2 Harness first Dedicated profile with tool-config pruning
3 System improves, not model Memory + skills compound across runs
4 Independent grader goal_judge + kanban tasks with acceptance criteria
5 Maker/checker split delegate_task verifier subagent
6 Timer, then cloud profile-created cronjob seeds kanban on 60s tick
7 Compose with workflows delegate_task batch + kanban deps
8 Memory State log + durable memory + skills
9 Distill into skills skill_manage patch-on-fail lifecycle
10 Fail safe Restricted profile + enabled_toolsets + repeat cap

Prerequisites

  • Hermes Agent with /goal and /subgoal commands
  • goal_judge auxiliary model configured
  • Kanban dispatcher, cronjob, skill_manage, and memory tools
  • A dedicated Hermes profile for running the loop

Loading

skill_view(name="loop-designer")
Changes

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.

  1. 2mo ago First seen · 34 lines · 336 tokens per session scan A 94a649d85ce9

Subscribe to this mod's changes

loop-designer AGENTS.md is an instructions file published in the GitHub repository groktopus/loop-designer (7 stars, last pushed 3mo ago), licensed MIT. It adds 336 tokens to every session, about $0.0013 per session on Opus 5.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.

Related

Other instructions, from other repositories

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens