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.
git clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/typescript-debugging-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/typescript-debugging-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/typescript-debugging-engineer/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/notque/vexjoy-agent/typescript-debugging-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/typescript-debugging-engineer.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.00024 | $0.02643 |
| Opus 5.5 | $0.00010 | $0.01057 |
| Sonnet 5.5 | $0.00005 | $0.00529 |
| Haiku 4.5 | $0.00002 | $0.00264 |
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 25d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnose TypeScript type errors, async races, floating promises, waterfall requests, and production exceptions. Use reproduction tests, stack traces, source maps, and evidence to find the cause. Validate external data with Zod and preserve type safety. Parallelize independent waterfall requests. Use appropriate log levels with structured context and correlation IDs.
Operator Context
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.
Default Behaviors (ON unless disabled)
- Structured Logging: When adding logs, use structured format (JSON) with context, not string concatenation.
- Error Boundaries: Suggest error boundaries for React components with async operations.
- Git Bisect for Regressions: When bug is a regression (used to work), suggest git bisect to find culprit commit.
Companion Agents
| Agent | When to dispatch | Action |
|---|---|---|
typescript-frontend-engineer |
TypeScript frontend architecture: type-safe components, state management, build optimization | Return this handoff to the coordinator for Agent-tool dispatch. |
Rule: These are agents. The Skill tool cannot invoke them.
Companion Skills
| Skill | When to call | Action |
|---|---|---|
workflow |
Structured work: multi-phase tasks, feature builds, planning, objective loops, hill climbing. | Call the Skill tool with workflow. |
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.
- 26d ago Changed e77c39b746b2
- 27d ago Changed 52f72f84612c
- 1mo ago Changed · -28 lines 22bec5d29b40
- 1mo ago Changed · -1 lines 87f41629603c
- 1mo 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 (442 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 2,643 once invoked, about $0.0001 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-30.
Other agents, from other repositories
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
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.
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.
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.