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.
curl -O https://raw.githubusercontent.com/bharath03-a/GitCortex/main/.claude/agents/gcx-java-tester.mdgit clone --depth 1 https://github.com/bharath03-a/GitCortexWrote 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/agents/bharath03-a/gitcortex/gcx-java-tester)<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.
<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>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.00050 | $0.00910 |
| Opus 5.5 | $0.00020 | $0.00364 |
| Sonnet 5.5 | $0.00010 | $0.00182 |
| Haiku 4.5 | $0.00005 | $0.00091 |
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.
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
- Ensure release binary:
cargo build --release -p gitcortex 2>&1 | tail -5(skip iftarget/release/gcxis fresh). - Run the harness for each repo:
scripts/lang-smoke.sh <git-url> <probe-symbol> <clone-name> - 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
Structnodes withContainsedges from outer class.
- Re-run
Java-specific red flags
Check these explicitly — most common failure modes:
- Inner classes as separate nodes:
class Outer { class Inner {} }—Innermust appear as its ownStructnode with aContainsedge fromOuter. Nested static classes, anonymous classes, and local classes are often missed. - Annotations not modeled:
@Override,@Autowired,@Entity— annotations themselves can beMacroor 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 nameImmutableList, notImmutableList<E>. Generic params must be stripped from names. interface→Trait: Javainterface Foo {}→Traitnode.abstract class Foo {}→Structwith metadata. Should not be conflated with concrete classes.Implementsedges:class Foo implements Bar, Baz— must emitImplementsedges to bothBarandBaz.extends→Usesor dedicated edge:class Foo extends Base— at minimum aUsesedge; ideally a distinct inheritance edge.- Static factory methods:
ImmutableList.of(...)— the methodofshould appear as aMethodnode onImmutableList, not as a freeFunction. - Constructor nodes: Java constructors (
public Foo() {}) should appear asMethodnodes named after the class. enumtypes: Javaenum Status { ACTIVE, INACTIVE }→Enumnode. Enum constants →Constantnodes withContainsedges.- Package declaration to
Module:package com.example.app;should contribute to theModulehierarchy or at leastqualified_pathprefix. - Generated code exclusion:
target/generated-sources/,*.generated.java— should be excluded per.gitcortex/ignore.
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.
- 2mo ago First seen · 59 lines · 50 tokens per session scan A 3271e23787fa
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.
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.
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.
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.
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'.
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.
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…