unified-ai-system: Instructions file for Codex

AGENTS.md

unified-ai-system AGENTS.md is an instructions file for Codex, OpenCode from happy520ai/unified-ai-system. It costs 602 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for the unified-ai-system project, including which teams own each area, which programming languages to use, and how to document changes.

In plain words
What is it for?
Use them when changing the agent console, gateway, shared packages, or tooling scripts, especially when choosing a language or preparing a pull request.
Why use it?
They reduce confusion about where code belongs and which conventions new changes must follow. They also help keep shared packages and public interfaces consistent.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

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

Reuse

Borrowing it

Nothing to install: this file belongs to happy520ai/unified-ai-system. 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/happy520ai/unified-ai-system/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/happy520ai/unified-ai-system

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 unified-ai-system AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/happy520ai/unified-ai-system/agents-md"><img src="https://agentmods.dev/badge/instructions/happy520ai/unified-ai-system/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 602 This file is loaded in full into every session.
When invoked 602 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.00602 $0.00602
Opus 5 $0.00301 $0.00301
Sonnet 5 $0.00120 $0.00120
Haiku 4.5 $0.00060 $0.00060

Measured 10d ago against content hash 11dff15c00a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

unified-ai-system 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 10d 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 · 73 lines

How it starts

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

Repository Guidance

Ownership

  • apps/agent-console owns operator interaction.
  • apps/ai-gateway-service owns gateway runtime and Workbench behavior.
  • packages/shared-contracts owns public protocol types.
  • packages/shared-sdk owns reusable clients and adapters.
  • packages/shared-config owns shared configuration.
  • packages/shared-utils owns implementation-neutral helpers.

Language and Module Policy

  • For new changes, apps/agent-console and apps/ai-gateway-service should prefer TypeScript for runtime behavior and refactors.
  • packages/* should remain TypeScript-first for contracts, SDKs, shared engines, and utility layers.
  • Tooling scripts under tools/*.mjs should remain Node.js ESM JavaScript.
  • Use JSON for schema and contract payloads, and Markdown for runbooks, evidence, and operator documentation.
  • Introducing a new runtime language (for example Go or Rust) requires a measured rationale, migration boundary, and compatibility plan in the PR.
  • For every PR that touches runtime code or scripts, follow Language Selection Playbook: define the workload, compare alternatives, document why the selected language is the best fit, and capture rollback/compatibility impact.
    PRs that do not include a Language Selection section using the playbook checklist are not considered merge-ready.

Public Repository Rules

  • Keep application entrypoints under apps/.
  • Keep reusable contracts, SDKs, configuration, and engines under packages/.
  • Do not add generated phase ledgers, one-off verifier trees, or committed runtime evidence to master.
  • Generated evidence belongs under apps/ai-gateway-service/evidence/ and is ignored except for its README.
  • Historical engineering artifacts belong on the archive branch, not in the public product tree.
  • Do not recreate legacy/.

Safety

  • Never read, print, or commit provider keys, .env, raw webhooks, or private authorization records.
  • Real provider calls require explicit scoped authorization.
  • Keep the local fake provider as the credential-free default.
  • Do not silently modify /chat, provider selection, deployment, or release behavior.
  • Do not claim production readiness, L5 autonomy, or AGI without independent evidence.

Read the full file on GitHub · 73 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. 10d ago First seen · 73 lines · 602 tokens per session scan A 11dff15c00a2

Subscribe to this mod's changes

unified-ai-system AGENTS.md is an instructions file published in the GitHub repository happy520ai/unified-ai-system (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 602 tokens to every session, about $0.0030 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.

Related

Other instructions, from other repositories

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,296 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,153 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

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

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

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,469 tokens