What is codesage AGENTS.md?

Project instructions for CodeSage, a Rust-based code intelligence engine that builds structural and meaning-based search over source code. They describe its workspace, GPU option, tests, linting, and pre-push checks.

Use them when developing, testing, linting, or preparing CodeSage changes for a Git push.

They make it clear how to build CodeSage correctly and how to catch formatting, lint, or test failures before pushing changes. They also explain that the CUDA build option is required when targeting a GPU.

How iliaal/codesage configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to iliaal/codesage. 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/iliaal/codesage/master/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/iliaal/codesage

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/iliaal/codesage/agents-md/github.svg)](https://agentmods.dev/instructions/iliaal/codesage/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/iliaal/codesage/agents-md"><img src="https://agentmods.dev/badge/instructions/iliaal/codesage/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/iliaal/codesage/agents-md"><img src="https://agentmods.dev/badge/instructions/iliaal/codesage/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 20,589 This file is loaded in full into every session.

When invoked 20,589 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.

Model	Per session	Once invoked
Fable 5.1	$0.20589	$0.20589
Opus 5.5	$0.08236	$0.08236
Sonnet 5.5	$0.04118	$0.04118
Haiku 4.5	$0.02059	$0.02059

Measured yesterday against content hash 98dfb98cd797, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

codesage 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 · 330 lines

How it starts

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

CodeSage

Code intelligence engine with structural graph and semantic search. Rust workspace, tree-sitter parsing, ONNX embedding inference, cross-encoder reranking, SQLite storage, MCP interface.

Build

cargo build                                    # all crates
cargo build --release -p codesage --features cuda  # release binary with GPU
cargo test --workspace                         # all tests
cargo clippy --workspace                       # lint

Always build with --features cuda when targeting GPU. The binary errors if GPU is requested in config but the cuda feature is missing; it does not silently fall back to CPU.

Sanity check before pushing

Run bash scripts/sanity-check.sh before git push when you've made code changes. It checks changelog/plugin metadata, Rust formatting and clippy, shell lint/format, workspace tests, and script/plugin regressions, stopping on the first failure. Pass --cuda to include CUDA clippy; the release workflow requires it. --fast skips workspace tests and script/plugin regressions while retaining the validation and lint gates; do not use it for releases.

cargo fmt --all applies changes in place; CI runs cargo fmt --all -- --check, which only reports the diff and exits nonzero. The script catches an edit made after the last format run (as in commit a43c51d) before CI does.

Crate map

Crate	Role	Depends on
`protocol`	Shared types (Symbol, Reference, SearchResult, etc.)	nothing
`parser`	File discovery, language detection, tree-sitter symbol/reference extraction	protocol
`storage`	SQLite schema, CRUD, sqlite-vec KNN	protocol
`embed`	ONNX embedding inference (Embedder), cross-encoder reranking (Reranker), chunking	protocol, ort, tokenizers, hf-hub
`features`	Feature-slice mapping, trust-boundary derivation	parser, storage, protocol
`graph`	Indexing orchestration, search pipeline, query API	parser, storage, embed, features, protocol
`cli`	`codesage` binary: CLI subcommands + MCP stdio shim + Unix-socket daemon	everything

Read the full file on GitHub · 330 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.

yesterday Changed · +19 tokens per session 98dfb98cd797
13d ago Changed · +6 lines · +1,222 tokens per session 8ed54bf61e04
14d ago Changed · +7 lines · +798 tokens per session 230a10fb9ade
16d ago Changed · +242 tokens per session 49ef81a46158
20d ago Changed · +2 lines · +371 tokens per session 8fdf2963d3e0
21d ago Changed · +4 lines · +827 tokens per session f4ca1c5e30c7
24d ago Changed · -49 tokens per session e49c18c09304
25d ago Changed · +7 lines · +3,841 tokens per session 09eb2092b8e1
1mo ago Changed · -1 lines · -22 tokens per session 4762681c6cb5
1mo ago First seen · 305 lines · 13,340 tokens per session scan A 94da39edc8d7

Subscribe to this mod's changes

codesage AGENTS.md is an instructions file published in the GitHub repository iliaal/codesage (21 stars, last pushed yesterday), licensed MIT. It adds 20,589 tokens to every session, about $0.0824 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-30.

Backend and APIs Languages Rust ai-agents code-intelligence code-search embeddings mcp

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 · 9,649 tokens

codesage: Instructions file for Codex

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

CodeSage

Build

Sanity check before pushing

Crate map

What this file has done since we first saw it

Other instructions, from other repositories

vscode buildNext.instructions.md

next.js AGENTS.md

vscode oss-third-party-notices.instructions.md

langchain AGENTS.md

vscode copilot-instructions.md

deepseek-harness AGENTS.md