GitCortex: Agent for Claude Code

.claude/agents/kuzu-cypher.md

kuzu-cypher is an agent for Claude Code from bharath03-a/GitCortex. It costs 62 tokens per session (546 once invoked), scanned A, original, MIT.

A specialist for writing and improving Cypher, the query language used by the Kuzu graph database, within the GitCortex codebase. It follows that project's schema, escaping helpers, query patterns, and Kuzu-specific rules.

In plain words
What is it for?
Use it to add or optimize queries in the Kuzu store, debug Kuzu errors, safely handle user-provided strings, and add tests for query behavior.
Why use it?
Graph queries can return wrong results, create security risks, or fail because Kuzu differs from other Cypher databases. This provides project-aware guidance instead of relying on generic database knowledge.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is bharath03-a/GitCortex's own configuration. It tells Claude Code how to work on GitCortex 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 GitCortex configures →

Reuse

Borrowing it

Nothing to install: this file belongs to bharath03-a/GitCortex. 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/bharath03-a/GitCortex/main/.claude/agents/kuzu-cypher.md
Clone the repo
git clone --depth 1 https://github.com/bharath03-a/GitCortex

Made for: Claude Code.

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 kuzu-cypher

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/bharath03-a/gitcortex/kuzu-cypher"><img src="https://agentmods.dev/badge/agents/bharath03-a/gitcortex/kuzu-cypher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 546 The whole file, excluding the scripts and references it only reads on demand.
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.00062 $0.00546
Opus 5.5 $0.00025 $0.00218
Sonnet 5.5 $0.00012 $0.00109
Haiku 4.5 $0.00006 $0.00055

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

Security

Grade A, and why

kuzu-cypher 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.

.claude/agents/kuzu-cypher.md · 39 lines

What it actually says

You write Cypher queries against the GitCortex KuzuDB schema.

Schema (live source: gitcortex-store/src/schema.rs)

Read it before writing any query. Do not rely on memory — schema evolves.

Kuzu dialect quirks (vs Neo4j)

  • Kuzu rejects LIMIT without an ORDER BY in some versions. Always pair them.
  • String literals must use the project's escape helper in gitcortex-store/src/kuzu/escape.rs. Do NOT inline user-provided strings into Cypher.
  • Kuzu has no MERGE. Use explicit MATCH / CREATE paths with the conv layer.
  • Parameter binding is via positional $param substitution in this codebase — check existing queries for the pattern before introducing a new style.
  • REL TABLE direction matters. MATCH (a)-[r:CALLS]->(b) and MATCH (a)<-[r:CALLS]-(b) are different queries with different costs.

Workflow

  1. Read crates/gitcortex-store/src/schema.rs for current node/rel tables.
  2. Read crates/gitcortex-store/src/kuzu/queries.rs for existing query patterns to match style.
  3. Read crates/gitcortex-store/src/kuzu/escape.rs before any user-string interpolation.
  4. Write query using the project's helpers, not raw format!.
  5. Add a #[cfg(test)] test in the same file if the query is non-trivial.
  6. Run cargo nextest run -p gitcortex-store.

Hard rules

  • Never build Cypher with raw format!("...{user_input}..."). Always go through escape.rs.
  • Never add LIMIT N without ORDER BY — Kuzu may error or return non-deterministic results.
  • Mutating queries (CREATE/SET/DELETE) only inside apply_diff codepath. Read queries elsewhere.
  • Flag any query that scans an unbounded relationship — branch graphs can grow large.

Output: the query, its expected cost class (O(1) hash lookup / O(degree) / O(graph)), and the test added.

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 · 39 lines · 62 tokens per session scan A 60e36b7a8a09

Subscribe to this mod's changes

kuzu-cypher is an agent published in the GitHub repository bharath03-a/GitCortex (8 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 546 once invoked, about $0.0002 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

Other agents, from other repositories

MS-SQL Database Administrator

Work with Microsoft SQL Server databases using the MS SQL extension.

github/awesome-copilot · 18 tokens

core-data-auditor

Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking.

CharlesWiltgen/Axiom · 28 tokens

lens

Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".

jeremylongshore/tons-of-skills-marketplace · 53 tokens

ecto-schema-designer

Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.

oliver-kriska/claude-elixir-phoenix · 30 tokens

django-migrations-specialist

Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…

AratKruglik/claude-sdlc · 85 tokens

database-architect

Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…

aayushostwal/nexus · 96 tokens