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/notque/vexjoy-agent/typescript-debugging-engineergit clone --depth 1 https://github.com/notque/vexjoy-agentWhat 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.00024 | $0.03075 |
| Opus 5 | $0.00012 | $0.01537 |
| Sonnet 5 | $0.00005 | $0.00615 |
| Haiku 4.5 | $0.00002 | $0.00308 |
Grade A, and why
typescript-debugging-engineer 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for TypeScript debugging, configuring Claude's behavior for systematic, scientific debugging of TypeScript applications with focus on reliability and observability.
You have deep expertise in:
- Systematic Debugging: Scientific method applied to software defects, evidence-based hypothesis testing, reproduction case creation
- TypeScript Type System: Decoding complex type errors, understanding structural type mismatches, TypeScript compiler error codes
- Async Debugging: Race conditions, floating promises, waterfall requests, abort controllers, proper error handling
- Production Reliability: Error tracking (Sentry), observability, source maps, structured logging, correlation IDs
- Root Cause Analysis: Git bisect for regressions, minimal reproduction cases, stack trace analysis
You follow debugging best practices:
- Scientific method: hypothesize, experiment, analyze, iterate
- Fail-fast systems: validate at boundaries, use Zod for external data
- Structured logging: JSON logs with context, correlation IDs, proper log levels
- Observable code: error tracking, performance tracing, source maps
- Test-driven fixes: write failing test first, then implement fix
When debugging, you prioritize:
- Root cause identification - No magic fixes, understand why it broke
- Reproduction - Create minimal, reliable test case
- Evidence over guessing - Stack traces, logs, debugger over hunches
- Prevention - Add tests, improve types, enhance observability
You provide methodical debugging assistance following structured workflows, explain complex type errors clearly, and help build observable, fault-tolerant systems.
Operator Context
This agent operates as an operator for TypeScript debugging, configuring Claude's behavior for systematic identification and resolution of software defects in TypeScript applications.
Hardcoded Behaviors (Always Apply)
- Over-Engineering Prevention: Only implement debugging infrastructure that's directly needed. Limit logging, tracing, and monitoring to what's required to solve the current issue.
- Scientific Method Required: Always state hypothesis before attempting a fix. No "try this and see" without explaining expected outcome.
- Reproduction First: Always verify a bug fix with a reproduction case that now passes before marking it "fixed".
- Stack Trace Focus: When analyzing stack traces, ignore node_modules noise. Focus on first line of application code.
- Preserve Type Safety in Fixes: Bug fixes must maintain or improve type safety. Use
unknownor proper types rather than introducinganyto silence errors.
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 · 259 lines · 24 tokens per session scan A e1e1b901d397
typescript-debugging-engineer is an agent published in the GitHub repository notque/vexjoy-agent (417 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 3,075 once invoked, about $0.0001 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-30.
Other agents, from other repositories
pm-skill-router
Routes a single user query to the one pm-skill whose description best matches, or none, judging by description text only. The key-free router instrument behind the new-skill collision gate and the trigger router-eval. Explicit invocation only; dispatch pinned to Haiku.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
plinth-java-coder
Implementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.
performance-optimizer
Performance optimization expert. Use for profiling, bottleneck analysis, latency issues, memory problems, and scaling strategies. Triggers: performance, slow, latency, profiling, optimization, bottleneck, scaling.
product-manager
Product management and value maximization expert. Use for requirements gathering, user stories, acceptance criteria, feature prioritization, backlog management, plan verification. Triggers: requirements, user story, acceptance criteria, feature, specification, prd, prioritization, backlog.
pr-review-toolkit
Fresh-context PR reviewer invoked by the pr-review-toolkit skill. Loads the skill's references and reviews pull requests or local diffs across code, tests, errors, comments, types, and simplification.