Gortex is a local code-intelligence engine that indexes one or more repositories into a knowledge graph and exposes information through a CLI, MCP server, API, and web interface. AI coding agents and IDEs use it to retrieve structured details about code such as symbols, call chains, routes, and cross-service relationships. The catalogue instruction configures coding agents to use Gortex.
Borrowing it
Nothing to install: this file belongs to zzet/gortex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zzet/gortex/main/CLAUDE.mdgit clone --depth 1 https://github.com/zzet/gortexWrote 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.
[](https://agentmods.dev/instructions/zzet/gortex/claude-md)<a href="https://agentmods.dev/instructions/zzet/gortex/claude-md"><img src="https://agentmods.dev/badge/instructions/zzet/gortex/claude-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.
<a href="https://agentmods.dev/instructions/zzet/gortex/claude-md"><img src="https://agentmods.dev/badge/instructions/zzet/gortex/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.05445 | $0.05445 |
| Opus 5.5 | $0.02178 | $0.02178 |
| Sonnet 5.5 | $0.01089 | $0.01089 |
| Haiku 4.5 | $0.00545 | $0.00545 |
Grade A, and why
gortex CLAUDE.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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gortex
Code intelligence engine written in Go. Indexes repositories into a knowledge graph held in a local SQLite store and exposes it via CLI and MCP Server.
Build & Test
CGO_CFLAGS="-O2 -g -fno-strict-aliasing" CGO_CXXFLAGS="-O2 -g -fno-strict-aliasing" \
go build -o gortex ./cmd/gortex/ # requires CGO (tree-sitter C bindings)
go test -race ./... # all test packages must pass
Gcc builds must disable strict aliasing in C and C++ dependency packages to avoid
tree-sitter heap corruption (#821).
The flags above preserve Go's default -O2 -g; make sets them automatically.
Building with clang (CC=clang CXX=clang++) is another option.
Codebase Overview
- Languages: go (primary)
- Entry point:
cmd/gortex/main.go - Source: 1,338 Go files (728 non-test) across the
cmd/andinternal/trees - Graph size: ~31k nodes, ~206k edges when the daemon indexes this repo
MANDATORY: Use Gortex's graph tools instead of Read/Grep/Glob
Gortex's workhorse tools are reachable two equivalent ways — over the registered MCP server, or via the equivalent gortex CLI verbs (gortex edit verify, gortex memory surface, gortex analyze, and gortex call <tool> for anything else; the verb reference is in docs/cli.md). Use whichever your harness has mounted — they are two front doors over the same handlers, and the daemon routes tool calls by name so the CLI reaches the full surface even under the core preset.
Either way, you MUST prefer graph queries over file reads on every task in this repo — search_symbols, find_usages, get_symbol_source, get_editing_context, smart_context, edit_symbol / edit_file / rename_symbol / batch_edit (or the matching gortex verbs). PreToolUse hooks deny Read / Grep / Glob against indexed source; the deny message names the right tool. The MCP server registers 180+ tools but by default publishes only a curated core preset (~34 dev-cycle workhorses) eagerly in tools/list, deferring the rest behind the tools_search discovery tool (the core/defer default — see docs/mcp.md). Opt into the full eager surface with GORTEX_TOOLS=full; GORTEX_LAZY_TOOLS=1 is the older all-or-nothing defer switch. The cross-project rule tables live in ~/.claude/CLAUDE.md — neither is restated here. This file carries only project-specific guidance.
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 · +6 lines · +118 tokens per session 4487c5fabbac
- 4d ago Changed · +62 tokens per session b1c90fca7a17
- 29d ago Changed · +1 lines · +93 tokens per session f0be112f1fab
- 1mo ago First seen · 134 lines · 5,172 tokens per session scan A 9fc95c3866ad
gortex CLAUDE.md is an instructions file published in the GitHub repository zzet/gortex (1,921 stars, last pushed today), licensed Apache-2.0. It adds 5,445 tokens to every session, about $0.0218 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.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.