agentmods.dev

Codex-Manager AGENTS.md

Repository instructions for Codex Manager, a desktop application with a web interface, native shell, local service, and database code.

In plain words
What is it for?
Use them when changing the user interface, desktop behavior, local services, database code, or communication between these parts.
Why use it?
They clarify which part of the repository owns each responsibility and how APIs, settings, and stored data should stay in sync.

Instructions file for CodexOpenCode

2.9k today A scan 1,221 tokens original MIT
View the source file qxcnm/Codex-Manager
Install

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.

agentmods
npx agentmods add instructions/qxcnm/codex-manager/agents-md
Clone the repo
git clone --depth 1 https://github.com/qxcnm/Codex-Manager

Made for: Codex, OpenCode.

Per session 1,221 This file is loaded in full into every session.
When invoked 1,221 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.01221 $0.01221
Opus 5 $0.00611 $0.00611
Sonnet 5 $0.00244 $0.00244
Haiku 4.5 $0.00122 $0.00122

Measured 2d ago against content hash a6ec1faeae6c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Codex-Manager 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.

AGENTS.md · 99 lines

How it starts

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

Repository Engineering Standards

This file applies to the whole CodexManager repository. For work under apps/, also read apps/AGENTS.md; that file contains the more specific frontend and Tauri rules.

1. Project Shape

  • apps/: Next.js frontend plus the Tauri desktop shell.
  • apps/src/: App Router UI, components, hooks, API clients, runtime helpers, i18n, and Zustand state.
  • apps/src-tauri/: Tauri v2 application shell, desktop lifecycle, tray/window behavior, native commands, and desktop RPC client code.
  • crates/core/: SQLite migrations, storage primitives, auth helpers, and core usage/account data structures.
  • crates/service/: local HTTP/RPC service, gateway routing, protocol adapters, account/API key/usage domains, plugins, app settings, and runtime sync.
  • crates/web/: service-mode Web UI shell, embedded static UI serving, and /api/runtime / /api/rpc proxy behavior.
  • crates/start/: service-mode launcher that starts service + web together.
  • scripts/, docker/, .github/: build, release, probe, container, and CI automation.

2. Ownership Boundaries

  • Keep UI behavior in apps/src/, desktop shell behavior in apps/src-tauri/, and service/gateway behavior in crates/service/.
  • Put schema and persistence foundation changes in crates/core/, especially SQLite migrations and reusable storage helpers.
  • Avoid expanding central entrypoints with unrelated orchestration. Large files should be treated as legacy surfaces; new substantial logic should move into focused modules, hooks, or domain helpers.
  • Do not mix release/script changes with product behavior unless the task explicitly requires it.

3. API, RPC, and Command Sync

  • Frontend code must call backend capabilities through typed wrappers in apps/src/lib/api/.
  • Desktop IPC should use the centralized invoke / invokeFirst helpers from @/lib/api/transport; do not use raw fetch() for desktop commands.
  • Service commands that require a service address should pass parameters through withAddr(). App-shell commands such as app_*, open_*, and window/update helpers may omit it when no service address is needed.
  • Web/service-mode fallback is allowed only through the existing transport stack: transport.ts, transport-web-commands.ts, rpc-http.ts, and fetchWithRetry.
  • When adding or renaming a backend command, keep the chain synchronized: Rust implementation, Tauri command registry when applicable, service RPC dispatch/Web command mapping when applicable, and the frontend API wrapper.
  • Preserve the existing underscore command names and camelCase RPC method mapping conventions.

Read the full file on GitHub · 99 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. 2d ago First seen · 99 lines · 1,221 tokens per session scan A a6ec1faeae6c

Subscribe to this mod's changes

Codex-Manager AGENTS.md is an instructions file published in the GitHub repository qxcnm/Codex-Manager (2,947 stars, last pushed today), licensed MIT. It adds 1,221 tokens to every session, about $0.0061 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.

Backend and APIs
Related

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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 · 6,785 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,345 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens