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-typescript-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-typescript-tester)<a href="https://agentmods.dev/agents/bharath03-a/gitcortex/gcx-typescript-tester"><img src="https://agentmods.dev/badge/agents/bharath03-a/gitcortex/gcx-typescript-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-typescript-tester"><img src="https://agentmods.dev/badge/agents/bharath03-a/gitcortex/gcx-typescript-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.00054 | $0.00854 |
| Opus 5.5 | $0.00022 | $0.00342 |
| Sonnet 5.5 | $0.00011 | $0.00171 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
gcx-typescript-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 — 58 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 TypeScript repositories.
Canonical test matrix
| Repo | Clone name | Probe symbol | Why |
|---|---|---|---|
| https://github.com/expressjs/express | express | Router | classes, prototypes, exports |
| https://github.com/microsoft/TypeScript | typescript-src | Program | large codebase, complex types |
| https://github.com/vercel/next.js | nextjs | NextConfig | type exports, interfaces |
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. - Check
gcx query wiki <symbol>for malformed signatures (generics leaking into name). - Inspect if
.d.tsdeclaration files are being indexed (they should be excluded).
- Re-run
TypeScript-specific red flags
Check these explicitly — most common failure modes:
interfacevsclassconflation: TypeScriptinterface Foo {}should map toTrait(or a dedicated kind), NOTStruct.class Foo {}→Struct. Verify withgcx query lookup-symbol.- Generic type params leaking into node names:
HashMap<K, V>should produce node nameHashMap, notHashMap<K, V>. Checknamefield in lookup output. .d.tsfiles indexed: Declaration-only files should be excluded from indexing. Iflookup-symbolreturns nodes sourced from.d.tsfiles, the parser is over-indexing.export typevsexport const: Type-only exports (export type Foo = ...) →TypeAlias. Value exports →ConstantorFunction. Should not be conflated.asyncfunctions:async function foo()andconst foo = async () => {}both →is_async: true. Arrow function form is commonly missed.- Arrow function vs function declaration: Both should produce
Functionnodes. Arrow functions assigned toconstare commonly skipped. Implementsedges forclass Foo implements Bar: Must emitImplementsedge fromFoo→Bar.Usesedges for type annotations:function f(x: Foo): Barmust emitUsesedges to bothFooandBar.- Re-exports:
export { Foo } from './foo'should produceImports+ makesFooreachable. - Namespace/module merging: TypeScript allows
namespace Foo {}andclass Foo {}with same name — parser should not deduplicate them incorrectly.
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 · 58 lines · 54 tokens per session scan A a021186c8016
gcx-typescript-tester is an agent published in the GitHub repository bharath03-a/GitCortex (8 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 854 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
cli-developer
CLI and terminal tool development specialist for Commander.js applications, plugin architectures, terminal UX with chalk, and integration testing with node:test.
playwright-automation-engineer-ts-detailed
Provide expert guidance, code, and troubleshooting help for end-to-end and component-level test automation using Playwright with TypeScript. Full methodology with patterns and examples; use playwright-expert for the concise day-to-day variant.
hcc-frontend-iqe-to-playwright-converter
Use this agent to convert IQE/Selenium tests to Playwright TypeScript. This agent implements proper Red Hat SSO authentication (global or isolated), converts fixtures and page objects, modernizes selectors and wait patterns, uses symbolic timeout constants, handles parametrized tests, and organizes converted files by…
testing-engineer
Testing specialist for Rust, TypeScript, and Luau/Lua projects focused on comprehensive test coverage, test infrastructure, and quality assurance. Applies the project's language rules from the stack profile. Use PROACTIVELY when adding new functionality that requires tests, investigating test failures, or setting up…
typescript-pro
Master TypeScript with advanced types, generics, and strict type safety. Handles complex type systems, decorators, and enterprise-grade patterns. Use PROACTIVELY for TypeScript architecture, type inference optimization, or advanced typing patterns.
test-generator
Use this agent to generate high-quality TypeScript unit tests for a target file or directory. Detects the host project's test runner (Jest, Vitest, node:test) and follows the project's documented testing standards.