code-meridian: Instructions file for Codex

AGENTS.md

code-meridian AGENTS.md is an instructions file for Codex, OpenCode from Driftya/code-meridian. It costs 999 tokens per session, scanned A, original, MIT.

Repository instructions for Driftya/code-meridian that tell automated coding agents how to behave and when to use CodeMeridian, a code-structure analysis tool.

In plain words
What is it for?
Use them when changing the Driftya/code-meridian repository, especially before edits, refactors, or work on specific classes and methods.
Why use it?
They reduce guesswork and help agents make small, checked changes that fit the repository's rules.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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 code-meridian AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/driftya/code-meridian/agents-md"><img src="https://agentmods.dev/badge/instructions/driftya/code-meridian/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 999 This file is loaded in full into every session.
When invoked 999 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.00999 $0.00999
Opus 5.5 $0.00400 $0.00400
Sonnet 5.5 $0.00200 $0.00200
Haiku 4.5 $0.00100 $0.00100

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

Security

Grade A, and why

code-meridian 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 15d 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 · 93 lines

How it starts

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

AGENTS.md

Short always-on guidance for automated agents working in this repository.

Read this first. Use the detailed references under docs/agent/ when the task needs more depth.

Behavior Expectations

  • Do not assume silently. State important assumptions.
  • If something is unclear, ask instead of guessing.
  • Prefer the simplest solution that solves the request.
  • Do not add speculative abstractions, flexibility, or features.
  • Make surgical changes only. Avoid unrelated refactors.
  • Match the existing style unless the task requires otherwise.
  • Remove only unused code introduced by your own change unless asked.
  • Define success criteria and verify them.
  • For bugs, prefer reproduce -> fix -> verify.
  • Every changed line should trace back to the request.

Required CodeMeridian Usage

Use CodeMeridian proactively. Prefer graph tools over terminal scans when the graph can answer the question.

Check get_project_profile(projectContext, targetPath?) before selecting language-specific edit tools. Markdown/text edits use document context and document_review; do not treat headings or filenames as callable symbols. Missing profiles and unaudited coverage remain unknown. PowerShell is detected but currently unsupported.

Trigger rules

Situation Tool to call
Before a non-trivial callable-code edit build_minimal_context
Before a Markdown/text edit get_project_profile, then search_documentation when document coverage is ready
Before editing a specific method/class resolve_exact_symbol, then get_context_for_editing
Before a refactor find_impact and find_test_shield
Before deleting code find_unreferenced
Before starting a feature analyze_feature_implementation_path, then find_implementation_surface for exact targets
Before trusting exact file targets check_graph_freshness or find_graph_drift
"How do X and Y relate?" find_connection
Frontend HTML/CSS/SCSS relationship work build_minimal_context, then find_connection or find_implementation_surface
Before renaming or deleting a frontend class/selector/style import find_impact
Investigating CSS/SCSS cascade or specificity issues find_frontend_cascade_conflicts
Looking for repeated style values or token extraction candidates find_duplicate_candidates
Looking for an existing implementation shape to mirror find_implementation_patterns
Looking for duplicate/refactor risk find_duplicate_candidates or find_similar_nodes
Looking for missing tests find_coverage_gaps
Searching docs/decisions search_documentation
Working with config find_config_definitions and find_config_usage
Looking for keyword-related context find_related_knowledge

Read the full file on GitHub · 93 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. 15d ago Changed · +3 lines · +84 tokens per session d14a17ede8e6
  2. 2mo ago First seen · 90 lines · 915 tokens per session scan A ab8401926d1e

Subscribe to this mod's changes

code-meridian AGENTS.md is an instructions file published in the GitHub repository Driftya/code-meridian (5 stars, last pushed 6d ago), licensed MIT. It adds 999 tokens to every session, about $0.0040 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

code-meridian AGENTS.md compared with instructions from other repositories

code-meridian AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
code-meridian AGENTS.mdDriftya/code-meridianInstructions file56d agoMITA999Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode