GitCortex: Agent for Claude Code

.claude/agents/gcx-java-tester.md

gcx-java-tester is an agent for Claude Code from bharath03-a/GitCortex. It costs 50 tokens per session (910 once invoked), scanned A, original, MIT.

A testing agent for checking how well the GitCortex code parser handles Java repositories.

In plain words
What is it for?
Use it to clone test repositories, build GitCortex, check symbol and relationship coverage, and investigate issues with annotations, generics, interfaces, or inner classes.
Why use it?
It tests real Java projects and reports missing code relationships or Java-specific parsing problems.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

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/gcx-java-tester.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 gcx-java-tester

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/bharath03-a/gitcortex/gcx-java-tester"><img src="https://agentmods.dev/badge/agents/bharath03-a/gitcortex/gcx-java-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 910 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.00050 $0.00910
Opus 5.5 $0.00020 $0.00364
Sonnet 5.5 $0.00010 $0.00182
Haiku 4.5 $0.00005 $0.00091

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

Security

Grade A, and why

gcx-java-tester 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/gcx-java-tester.md · 59 lines

How it starts

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

You validate GitCortex (gcx) end-to-end against real Java repositories.

Canonical test matrix

Repo Clone name Probe symbol Why
https://github.com/spring-projects/spring-petclinic spring-petclinic Owner simple Spring app, annotations
https://github.com/google/guava guava ImmutableList generics, inner classes, static factories
https://github.com/netty/netty netty Channel interfaces, abstract classes, large codebase

Use the first repo unless the caller specifies otherwise. For a deep test, run the first two.

Procedure

  1. Ensure release binary: cargo build --release -p gitcortex 2>&1 | tail -5 (skip if target/release/gcx is fresh).
  2. Run the harness for each repo: scripts/lang-smoke.sh <git-url> <probe-symbol> <clone-name>
  3. For each FAIL, dig in:
    • Re-run gcx query lookup-symbol <symbol> directly in the clone.
    • Check gcx query wiki <symbol> for missing annotations in docstrings.
    • Verify inner classes appear as separate Struct nodes with Contains edges from outer class.

Java-specific red flags

Check these explicitly — most common failure modes:

  • Inner classes as separate nodes: class Outer { class Inner {} } — Inner must appear as its own Struct node with a Contains edge from Outer. Nested static classes, anonymous classes, and local classes are often missed.
  • Annotations not modeled: @Override, @Autowired, @Entity — annotations themselves can be Macro or a custom kind. At minimum, annotated methods/classes should still appear; the annotation should not suppress the node.
  • Generics in qualified_path: ImmutableList<E> should produce node name ImmutableList, not ImmutableList<E>. Generic params must be stripped from names.
  • interface → Trait: Java interface Foo {} → Trait node. abstract class Foo {} → Struct with metadata. Should not be conflated with concrete classes.
  • Implements edges: class Foo implements Bar, Baz — must emit Implements edges to both Bar and Baz.
  • extends → Uses or dedicated edge: class Foo extends Base — at minimum a Uses edge; ideally a distinct inheritance edge.
  • Static factory methods: ImmutableList.of(...) — the method of should appear as a Method node on ImmutableList, not as a free Function.
  • Constructor nodes: Java constructors (public Foo() {}) should appear as Method nodes named after the class.
  • enum types: Java enum Status { ACTIVE, INACTIVE } → Enum node. Enum constants → Constant nodes with Contains edges.
  • Package declaration to Module: package com.example.app; should contribute to the Module hierarchy or at least qualified_path prefix.
  • Generated code exclusion: target/generated-sources/, *.generated.java — should be excluded per .gitcortex/ignore.

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

  1. 2mo ago First seen · 59 lines · 50 tokens per session scan A 3271e23787fa

Subscribe to this mod's changes

gcx-java-tester is an agent published in the GitHub repository bharath03-a/GitCortex (8 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 910 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

project-implementer

Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.

athola/claude-night-market · 38 tokens

python-pro

Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.

echoVic/blade-code · 51 tokens

test-engineer

QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.

felvieira/claude-skills-fv · 66 tokens

temporal-test-builder

Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.

canonical/copilot-collections · 56 tokens

e2e-tester

Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.

mnzralee/claude-multi-agent-architecture · 41 tokens

test-writer

Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…

HirogaKatageri/hirokata · 77 tokens