endy: Instructions file for Codex

AGENTS.md

endy AGENTS.md is an instructions file for Codex, OpenCode from trentisiete/endy. It costs 3,029 tokens per session, scanned A, original, MIT.

Project instructions for endy, a multi-agent coding setup that connects several command-line AI assistants and defines their roles and usage details.

In plain words
What is it for?
Use them when coordinating Codex, OpenCode, CommandCode, Hermes, or the setup's delegation workflows.
Why use it?
They help an agent choose the appropriate assistant and avoid command-line or delegation mistakes.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions subagents; mentions Claude Code; reads ~/.codex paths.

This is trentisiete/endy's own configuration. It tells Codex and OpenCode how to work on endy 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 endy configures →

Reuse

Borrowing it

Nothing to install: this file belongs to trentisiete/endy. 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/trentisiete/endy/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/trentisiete/endy

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 endy AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/trentisiete/endy/agents-md/github.svg)](https://agentmods.dev/instructions/trentisiete/endy/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/trentisiete/endy/agents-md"><img src="https://agentmods.dev/badge/instructions/trentisiete/endy/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 endy AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/trentisiete/endy/agents-md"><img src="https://agentmods.dev/badge/instructions/trentisiete/endy/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,029 This file is loaded in full into every session.
When invoked 3,029 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.03029 $0.03029
Opus 5.5 $0.01212 $0.01212
Sonnet 5.5 $0.00606 $0.00606
Haiku 4.5 $0.00303 $0.00303

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

Security

Grade A, and why

endy 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 1mo 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 · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

endy — multi-agent coding stack

You're running inside endy, a hybrid bash + skill stack that wires several coding-agent CLIs together. This file is loaded by every supported agent (Codex, OpenCode, CommandCode/cmd, and — when re-enabled — Claude Code) via their global AGENTS.md mechanism. Hermes loads its own context via ~/.hermes/SOUL.md separately.

Read it once at the start of a session and keep it in mind. Don't quote it back at the user.

Who's in the stack

Agent Strength When to pick it
Codex (codex) Long-context planning, GitHub-Copilot-backed gpt-5.5 with xhigh reasoning Default orchestrator. Use Codex itself unless the task fits a specialist.
OpenCode (opencode) Fast multi-model worker, default agent "build" runs on big-pickle Mechanical refactors, test-writing, codemods. Cheap and fast.
CommandCode (cmd) "Taste-1" model — purpose-built for code aesthetics "Does this read well / match the codebase's idioms?" Nothing else is this good for that.
Hermes (hermes) Tool-calling-tuned models from Nous Research; rich plugin/MCP/skill ecosystem Open-ended agentic work, when you want a specific Nous model, or when you want a parallel orchestrator independent of Codex.
Gemini CLI (gemini) Google Gemini, generous free daily quota Free-tier worker. Use for routine refactors, summaries, exploratory work — keep paid agents for the parts that need them.

Delegation primitives

Three ways to hand work off — pick deliberately, the differences matter:

  1. In-Codex personas (.codex/agents/architect.toml, reviewer.toml, researcher.toml). The native multi_agent toolset spawns these inside Codex itself — no extra processes. Cheap and clean for orchestrator-side roles.
  2. Short bash inline — for blocking calls that finish in a few minutes:
    • opencode run [--agent <persona>] "<prompt>"
    • cmd --skip-onboarding --trust [--yolo] -p "<prompt>"
    • hermes chat -Q --accept-hooks [--skills <name>] -q "<prompt>"
    • gemini [--model <m>] [--yolo] -p "<prompt>" The skill endy-delegate covers when to use a persona vs ad-hoc inline.
  3. Long detached runs — for unsupervised work that may take 5+ minutes and needs full permissions OK:
    • endy spawn <agent> [--persona <name>] -- "<prompt>"
    • Returns a TASK_ID immediately; agent runs in a fresh tmux window.
    • Track with endy watch list / endy watch log <id>.

Read the full file on GitHub · 128 lines

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. 1mo ago First seen · 128 lines · 3,029 tokens per session scan A 9e30948bf690

Subscribe to this mod's changes

endy AGENTS.md is an instructions file published in the GitHub repository trentisiete/endy (7 stars, last pushed 5mo ago), licensed MIT. It adds 3,029 tokens to every session, about $0.0121 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,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens