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/bjornmelin/codex-toolloop/agents-mdgit clone --depth 1 https://github.com/BjornMelin/codex-toolloopWrote 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/bjornmelin/codex-toolloop/agents-md)<a href="https://agentmods.dev/instructions/bjornmelin/codex-toolloop/agents-md"><img src="https://agentmods.dev/badge/instructions/bjornmelin/codex-toolloop/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.01422 | $0.01422 |
| Opus 5 | $0.00711 | $0.00711 |
| Sonnet 5 | $0.00284 | $0.00284 |
| Haiku 4.5 | $0.00142 | $0.00142 |
Grade A, and why
codex-toolloop 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 3d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Setup
- Node.js 24+ (
.nvmrc), pnpm (Corepack:corepack enable). - Copy
.env.exampleto.env; never commit real keys.
Project Layout
apps/cli/: CLI entrypoint (apps/cli/src/index.ts).packages/: workspace packagespackages/codex-toolloop/: core runtime scaffoldpackages/codex/: Codex backends (app-server / exec / sdk)packages/mcp/: MCP tool substrate + policypackages/workflows/: workflow + routing utilitiespackages/testkit/: fixtures/mocks/temp dirs
src/: root exports + prototype workflowstests/unit/: Vitest runtime tests;tests/type/:*.test-d.tsdocs/: PRD, ADRs (docs/adr/), specs (docs/specs/)examples/: runnable scripts (pnpm examples:*)
Commands
pnpm install
pnpm dev:cli -- doctor
pnpm build
pnpm fix:typecheck # required before finishing work
pnpm test
pnpm test:watch
pnpm examples:basic
Codex app-server schema upgrades
- If pinned
@openai/codexversion changes, runpnpm codex:genand update integration code for protocol deltas. - Guide:
docs/codex-app-server-protocol.md(ADR 0013/0014, SPEC 023/024-029). - When Codex SDK is involved, use the
$codex-sdkskill guide.
Turborepo (Vercel)
- Use
turbo run buildon Vercel (filters inferred by root). - In
turbo.json, definetasks.build.outputsfor each framework output dir.- Next.js:
[".next/**", "!.next/cache/**"]
- Next.js:
- Never include
.next/cache/**in outputs. - Declare task
env+globalEnvto avoid stale cache hits. - Validate remote caching locally:
turbo run build, then inspectnode_modules/.cache/turbo.
Style
- TypeScript ESM (NodeNext),
strict,noUncheckedIndexedAccess,exactOptionalPropertyTypes. - Biome (
biome.json): 2-space indent, 80-col. - Exported schemas use
...Schema; keep exports small and explicit.
Development Standards
Required before you finish:
pnpm -s fix:typecheck (runs pnpm -s fix, pnpm -s typecheck, pnpm -s test). Keep its 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.
- 3d ago First seen · 114 lines · 1,422 tokens per session scan A 25d56d43fde8
codex-toolloop AGENTS.md is an instructions file published in the GitHub repository BjornMelin/codex-toolloop (1 stars, last pushed 5mo ago), licensed MIT. It adds 1,422 tokens to every session, about $0.0071 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
apm python.instructions.md
Python development guidelines.
CodexPotter AGENTS.md
Instructions for breezewish/CodexPotter, covering repository guidelines, workflow principles, engineering rules, core principles: simplicity & readability and better maintainability.
copilot-proxy-api CLAUDE.md
Instructions for voidsteed/copilot-proxy-api, covering claude.md, project overview, common commands, architecture and entry points & cli structure.
OpenMicro AGENTS.md
Instructions for stephenleo/OpenMicro, covering openmicro — project conventions and releases.
squarebox CLAUDE.md
Instructions for SquareWaveSystems/squarebox, covering claude.md, agent skills, issue tracker, triage labels and domain docs.
SubFrame AGENTS.md
Instructions for Codename-11/SubFrame, covering subframe - subframe project, core working principle, relationship to native ai tools, session start and concurrent work & worktrees.