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-python-testergit 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.00050 | $0.00773 |
| Opus 5 | $0.00025 | $0.00387 |
| Sonnet 5 | $0.00010 | $0.00155 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
gcx-python-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 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 — 57 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 Python repositories.
Canonical test matrix
| Repo | Clone name | Probe symbol | Why |
|---|---|---|---|
| https://github.com/psf/requests | requests | Session | class + methods + imports |
| https://github.com/pallets/flask | flask | Flask | class inheritance, decorators |
| https://github.com/django/django | django | Model | large codebase, abstract classes |
Use the first repo unless the caller specifies otherwise. For a deep test, run all three.
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. - For wiki issues, check
gcx query wiki <symbol>output for malformed markdown. - For empty results, check if the tree-sitter Python grammar matched the file correctly.
- Re-run
Python-specific red flags
Check these explicitly — they are the most common failure modes:
- Decorator nodes missing:
@property,@staticmethod,@classmethod— the decorated function should still appear as aMethodnode. If missing, thedecorationtree-sitter node is being skipped. async defnot flagged:is_asyncmust betruefor coroutine functions. Verify withgcx query wiki <async_function_name>.- Class methods vs. functions confused: Top-level functions →
Function. Methods inside a class →Method. Check thekindfield ingcx query lookup-symbol. __init__/ dunder methods: Should appear asMethodnodes, not filtered out.- Nested classes: Inner classes should be
Structnodes withContainsedges from the outer class. Importsedge coverage:import os,from pathlib import Path,from . import utils— all three import forms should produceImportsedges.qualified_pathformat: Should bemodule/submodule::ClassName::method_name, not raw symbol names..d.ts-equivalent.pyistubs: Should NOT be indexed (they're type stubs, not source).__all__exports: Not required to be modeled, but if the parser emits them, they should beConstantnodes.
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 · 57 lines · 50 tokens per session scan A 24379673c0ef
gcx-python-tester is an agent published in the GitHub repository bharath03-a/GitCortex (7 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 773 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.