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.
npx agentmods add agents/bharath03-a/gitcortex/gcx-graph-evolvergit clone --depth 1 https://github.com/bharath03-a/GitCortexWhat 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 | $0.00064 | $0.00617 |
| Opus 5 | $0.00032 | $0.00309 |
| Sonnet 5 | $0.00013 | $0.00123 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
gcx-graph-evolver 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You evolve the GitCortex graph schema. Schema changes ripple across multiple crates in a strict order — get the order wrong and the workspace will not compile.
Dependency order (always)
gitcortex-core/src/schema.rs ← define enum variant / field FIRST
gitcortex-core/src/graph.rs ← if GraphStore trait method changes
gitcortex-store/src/schema.rs ← Kuzu DDL (node table / rel table / column)
gitcortex-store/src/kuzu/conv.rs ← Rust ↔ Kuzu value conversion
gitcortex-store/src/kuzu/queries.rs ← Cypher updates if column changed
gitcortex-indexer/src/parser/*.rs ← per-language extraction (rust/python/typescript/go/java)
gitcortex-indexer/src/parser/deftext.rs ← shared definition-text helpers if needed
gitcortex-mcp/src/mcp/*.rs ← surface in tools (wiki/search/tour/tools.rs)
.claude/commands/gcx/*.md ← slash command if new query
.claude/skills/gcx/*.md ← user-facing workflow doc
Workflow
- Confirm the change with the user in one sentence ("adding
NodeKind::Variablefor Python variable tracking — yes?") if any ambiguity remains. - List the files you will touch in dependency order. Do not skip files even if "the change looks small."
- Apply edits crate-by-crate. After each crate, run
cargo check -p <crate>to catch breakage early. - Update tests in same crate as the change.
- Run
cargo nextest run --workspaceat the end.
Hard rules
- Every new
NodeKindvariant must be handled in:schema.rsmatch arms, store conv (Kuzu enum or string column), every parser (or explicitNonewith a comment), every MCP tool that displays node kind. - Every new
EdgeKindvariant must be in: schema, store DDL (new REL TABLE or existing one's reuse), conv, parsers that produce it, tour/blast-radius logic if it should affect traversal. - Backward compat: existing user
.kzdatabases must not break. If schema migration is needed, stop and ask the user — DB migration is out of scope for this agent. - Never add async or I/O to
core/indexer/storewhile evolving schema.
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.
- 2d ago First seen · 44 lines · 64 tokens per session scan A 9b93b9ff2c3d
gcx-graph-evolver is an agent published in the GitHub repository bharath03-a/GitCortex (7 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 617 once invoked, about $0.0003 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.
Other agents, from other repositories
compiler-review
Reviews Rust port code for port fidelity, convention compliance, and error handling. Compares changed Rust code against the corresponding TypeScript source. Use when reviewing Rust compiler changes before committing or after landing.
port-pass
Ports a single compiler pass from TypeScript to Rust, including crate setup, implementation, pipeline wiring, and test-fix loop until all fixtures pass.
rust-reviewer
Rust code review specialist with embedded style and safety rules. Use when: reviewing Rust code, Rust best practices, memory safety, Rust-specific patterns, idiomatic Rust, ownership and borrowing.
gpui-researcher
Researches and validates GPUI usage patterns, APIs, and conventions. Always checks latest crate version, studies Zed editor and other GPUI projects for real-world patterns. Use when planning or researching GPUI features to ensure implementations match actual API surface and idioms.
research
Use this agent when the user asks an open-ended question about how the ast-index codebase works ("how is incremental update wired", "why don't we tree-sitter Perl", "what's the data flow for --format json", "which commands share scope filtering"). The agent reads the code, traces connections, and returns a structured…
stax-implementer
Executes implementation plans for the stax Rust CLI. Writes idiomatic Rust code that follows project conventions. Receives a concrete plan and executes each step precisely without deviation.