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/mideco-tech/codex-tg/agents-mdgit clone --depth 1 https://github.com/mideco-tech/codex-tgWhat 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.02868 | $0.02868 |
| Opus 5 | $0.01434 | $0.01434 |
| Sonnet 5 | $0.00574 | $0.00574 |
| Haiku 4.5 | $0.00287 | $0.00287 |
Grade A, and why
codex-tg 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS
Purpose: help AI agents work on codex-tg without increasing complexity or weakening the operator-facing Telegram control loop.
Good code is code that is easy to understand, change, test, and safely extend. Good agent work is evidence-backed, small in scope, and validated through the same surfaces the operator uses.
Repository Purpose
codex-tg is a Go daemon evolving into a local Codex Control Plane. Telegram is the first production adapter for observing, steering, approving, and routing local Codex App Server work.
The repo is public-facing. Keep every change safe for open-source publication: no private paths, tokens, Telegram ids, local sessions, databases, logs, screenshots with private data, or environment-specific credentials.
Working Mode
- First understand the current design. Read nearby code, tests, ADRs, and
docs/testing/regression-map.mdwhen it exists before editing. - Do not treat a vague request as enough context. Ask focused questions when requirements, constraints, or tradeoffs are unclear and cannot be discovered safely.
- Prefer small steps: inspect -> plan -> test -> implement -> refactor -> validate.
- Do not generate large rewrites, broad refactors, or speculative frameworks unless the task explicitly requires them.
- Build what is needed now. Avoid adding libraries, build tools, abstractions, or cross-platform machinery without an immediate reason.
- Match the current user's language for working plans, handoffs, and status updates when clear. Public README, wiki, demo, release notes, and GitHub-facing docs may stay English-first.
Agent Workflow Kernel
- Do not start coding vague work. For unclear features, run alignment first: ask focused questions, lock goal, non-goals, UX, data, tests, and acceptance.
- Feature work needs a destination before implementation: a short issue, feature brief, or equivalent written target.
- Slice vertically. Prefer one small end-to-end behavior over horizontal phases such as storage first, daemon later, UI last.
- Use TDD for non-trivial behavior changes and bug fixes: failing or updated test, minimal implementation, refactor, targeted checks.
- Use fresh-context review for meaningful changes. The reviewer should inspect issue/brief, diff, tests, ADR/rules, and validation output, not the implementation chat.
- Human/live QA remains required for Telegram-facing behavior when a live contour is available.
- After compaction, context reset, or handoff, reread this file first, then pull only the docs called out by the Context Pull Map.
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 · 178 lines · 2,868 tokens per session scan A 513fdfe8941f
codex-tg AGENTS.md is an instructions file published in the GitHub repository mideco-tech/codex-tg (28 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 2,868 tokens to every session, about $0.0143 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
hermes-codex-operator AGENTS.md
Instructions for AlekseiUL/hermes-codex-operator, a project described as: A local-first operator that turns plain-language ideas into tracked, verified Codex work—planned by Hermes, executed by Codex, and explained back to you.
Lody AGENTS.md
Instructions for LodyAI/Lody, covering repository guidelines, context maintenance, repository boundary, project map and checks and commits.
zot AGENTS.md
Instructions for patriceckhart/zot, covering working agreement for zot, product intent, starting a task, code ownership map and correctness contracts.
parallel-code CLAUDE.md
Instructions for johannesjo/parallel-code, covering parallel code, stack, commands, project structure and conventions.
cezar AGENTS.md
Instructions for open-mercato/cezar, covering agents.md — working in this repository, zero config, changing a mechanism that already works, the http api and repository layout.
phi AGENTS.md
Instructions for pulseaiclub/phi, covering phi, communication preferences, constraints, contributor guidelines and commands.