veridge: Instructions file for Codex

AGENTS.md

veridge AGENTS.md is an instructions file for Codex, OpenCode from galimar/veridge. It costs 511 tokens per session, scanned A, original, MIT.

A project instruction file for coding agents working on Veridge, a tool that builds a searchable map of a software project for people and AI assistants. It sets the project’s design rules, setup steps, tests, and code layout.

In plain words
What is it for?
Use it when modifying Veridge, running its checks, adding tests, or deciding where new code belongs.
Why use it?
It gives agents the project context and constraints they need before making changes, reducing the risk of broken tests, extra dependencies, or unwanted edits to source files.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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 veridge AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/galimar/veridge/agents-md"><img src="https://agentmods.dev/badge/instructions/galimar/veridge/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 511 This file is loaded in full into every session.
When invoked 511 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.00511 $0.00511
Opus 5.5 $0.00204 $0.00204
Sonnet 5.5 $0.00102 $0.00102
Haiku 4.5 $0.00051 $0.00051

Measured 2mo ago against content hash 366dc449dc8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

veridge 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 2mo 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 · 41 lines

What it actually says

AGENTS.md — working on Veridge

Veridge builds an always-fresh, low-token graph of a whole project (files + symbols + areas + decisions + git sessions), ranks it with PageRank, and serves token-budgeted slices to AI assistants and humans. The core has zero runtime dependencies (Python standard library only).

Setup & checks

pip install -e ".[dev,mcp,treesitter]"
ruff check veridge tests      # must pass
pytest -q                     # must pass

Every change must keep ruff and pytest green, and add/adjust tests for behaviour changes.

Design principles (do not break)

read-only on the user's sources · zero-deps core (any new dependency goes behind an optional extra, never in the core) · low-token (queries return structure, never file contents) · ranked (relevance from the graph, not raw counts) · deterministic (nodes and edges are sorted on serialization → reproducible graph.json). No LLM builds the graph.

Layout

  • model.py — typed nodes/edges + indexed adjacency (O(degree) queries)
  • walk.py / ignore.py / classify.py — file enumeration and typing
  • parse_python.py (stdlib ast) + treesitter.py (optional extra) — symbols, imports, calls
  • parse_docs.py — references (links / wikilinks / prose paths) + decision ids
  • indexer.py — assembles the graph; sessions.py — git history
  • rank.py (PageRank) · budget.py (token cost) · query.py (map / find / neighbors / focus / impact / tour / why)
  • freshness.py (manifest + anti-drift gate) · store.py (.veridge/) · watch.py · export.py · integrate.py
  • viewer.py + ui/template.html — offline canvas graph · cli.py · mcp_server.py

More

README.md (usage), ROADMAP.md (plan & what's intentionally out of scope), CONTRIBUTING.md (PR guidance), docs/graph-format.md (the graph.json schema).

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. 2mo ago First seen · 41 lines · 511 tokens per session scan A 366dc449dc8e

Subscribe to this mod's changes

veridge AGENTS.md is an instructions file published in the GitHub repository galimar/veridge (1 stars, last pushed 4mo ago), licensed MIT. It adds 511 tokens to every session, about $0.0020 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

veridge AGENTS.md compared with instructions from other repositories

veridge AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
veridge AGENTS.mdgalimar/veridgeInstructions file14mo agoMITA511Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,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