code-intel-platform AGENTS.md

A set of project instructions for the code-intel-platform repository. It defines rules for investigating source code and using tools before editing or committing.

In plain words
What is it for?
Use it when working in that repository, especially before investigating symbols, changing code, staging files, or committing.
Why use it?
It gives an agent a consistent workflow for finding code, checking the impact of changes, and following repository-specific commit rules.

Instructions file for CodexOpenCode

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/vohongtho/code-intel-platform/agents-md
Clone the repo
git clone --depth 1 https://github.com/vohongtho/code-intel-platform

Made for: Codex, OpenCode.

Per session 721 This file is loaded in full into every session.
When invoked 721 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.00721 $0.00721
Opus 5 $0.00360 $0.00360
Sonnet 5 $0.00144 $0.00144
Haiku 4.5 $0.00072 $0.00072

Measured yesterday against content hash 6728ab62c882, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-intel-platform 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 yesterday.

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 · 65 lines

How it starts

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

Source Code

/home/thomas/working/other/code-intel-platform

RULE

  1. DO NOT USE SUB AGENT
  2. Before run git add and git commit should get confirm from me
  3. The message generate for git commit DO NOT CONTENT: "Amp-Thread-ID:" "Co-authored-by: ***"
  4. Before run git add, if change need to update into readme.md, Should update

Tool Usage Rules (MANDATORY)

code-intel — Always Investigate First (before reading any file)

code-intel search "<concept>"   # FIRST: find symbols by concept
code-intel inspect <symbol>     # callers, callees, file location
code-intel impact <symbol>      # blast radius BEFORE editing
  • NEVER open a file cold — always code-intel search first.
  • NEVER grep for symbols — use code-intel search instead.
  • NEVER edit a symbol without running code-intel impact first.

rtk — Use for compact shell output

rtk read <file>            # token-efficient file read
rtk grep <pattern> <file>  # compact grep
rtk git log                # compact git log
rtk test <cmd>             # show only failures
rtk err <cmd>              # show only errors/warnings
rtk diff                   # condensed diff
rtk smart <cmd>            # 2-line heuristic summary

Code Intelligence — code-intel-platform

Auto-managed by code-intel analyze (v1.0.4) — re-running it overwrites this block. Put durable notes below <!-- code-intel:end -->.

code-intel keeps a symbol / call-graph index of this repo. It complements reading files, it doesn't replace it — on a repo this size, read files directly for most work and reach for code-intel when you need the call graph.

Reach for it when you need

  • Blast radius before changing a shared symbolcode-intel impact <symbol> (reverse call graph). Flag ≥ 5 direct callers to the user as higher-risk.
  • PR review scopecode-intel pr-impact --base master --head HEAD
  • Callers / callees of a symbolcode-intel inspect <symbol>
  • Concept search across filescode-intel search "<concept>"
  • Tracing an execution pathcode-intel query "TRAVERSE CALLS FROM '<symbol>' DEPTH 3"

Read the full file on GitHub · 65 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. yesterday First seen · 65 lines · 721 tokens per session scan A 6728ab62c882

Subscribe to this mod's changes

code-intel-platform AGENTS.md is an instructions file published in the GitHub repository vohongtho/code-intel-platform (3 stars, last pushed 5d ago), licensed MIT. It adds 721 tokens to every session, about $0.0036 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

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

buildNext

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

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

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

spec-kit 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,040 tokens

langchain 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