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 skills add dork-labs/dorkos --skill debugging-typescript-errorsgit clone --depth 1 https://github.com/dork-labs/dorkosWrote 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/skills/dork-labs/dorkos/debugging-typescript-errors)<a href="https://agentmods.dev/skills/dork-labs/dorkos/debugging-typescript-errors"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/debugging-typescript-errors/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/skills/dork-labs/dorkos/debugging-typescript-errors"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/debugging-typescript-errors.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.00039 | $0.00399 |
| Opus 5.5 | $0.00016 | $0.00160 |
| Sonnet 5.5 | $0.00008 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
debugging-typescript-errors 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 1mo 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.
What it actually says
Debugging TypeScript Errors
Overview
This is the shared-skill replacement for the legacy Claude Code /debug:types workflow.
Use it when TypeScript errors need real diagnosis rather than cargo-cult assertions or broad type loosening.
Read First
Before acting, read:
.agents/skills/debugging-systematically/SKILL.mdAGENTS.md
Core Workflow
- Collect the error
- use the provided error text when available
- otherwise run the narrowest useful typecheck scope
- Parse the compiler signal
- error code
- file and location
- expected vs actual type
- Read the surrounding code
- never propose a fix before reading the file
- Trace the type source
- where the actual type comes from
- where the expected type is defined
- where inference or narrowing goes wrong
- Classify the problem
- wrong data
- wrong type definition
- missing narrowing
- generic inference failure
- invalid assertion
- Apply the smallest correct fix
- fix data before widening types
- fix definitions before forcing assertions
- use assertions only as a last resort
- Re-run typecheck
- confirm the original error is gone
- check that no new related errors were introduced
Cross-Agent Rules
- Treat this skill as the portable replacement for
/debug:types. - Keep a short execution plan, but do not depend on a tool-specific todo API.
- Ask bounded clarification only when the repair strategy changes system behavior or type contracts materially.
- Prefer preserving strictness over silencing the compiler.
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.
- 1mo ago First seen · 56 lines · 39 tokens per session scan A 2dbae2b36d6f
debugging-typescript-errors is a skill published in the GitHub repository dork-labs/dorkos (12 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 399 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 skills, from other repositories
typescript-circular-dependency
Detect and resolve TypeScript/JavaScript circular import dependencies. Use when: (1) "Cannot access 'X' before initialization" at runtime, (2) Import returns undefined unexpectedly, (3) "ReferenceError: Cannot access X before initialization", (4) Type errors that disappear when you change import order, (5) Jest/Vitest…
ts-debug
TypeScript/Node debugging expert. Use when the user needs to debug, profile, or trace TypeScript or Node.js code — e.g. "how do I debug this", "find the memory leak", "why is this slow", "add a breakpoint", "profile this function", "why won't the process exit".
typescript-conventions
Use when a ticket adds or changes TypeScript/JavaScript code and it must follow the repo's TS conventions — strict mode typing, typescript-eslint type-aware rules, async correctness (no floating promises, bounded fan-out), boundary validation instead of casts, module/import hygiene, Node resource and concurrency…
strict-typescript
Enforce strict TypeScript compiler settings and type narrowing patterns. Use when the user creates a new TypeScript project, configures tsconfig.json, encounters null/undefined errors, deals with indexed access issues, or asks about strict mode, type safety, or narrowing techniques.
ide-type-mismatch-fix
Diagnose and fix TypeScript/language type errors using LSP diagnostics, hover, and code actions. For each type error, fetches the expected vs actual types, surfaces quickfix suggestions, and optionally applies them. Use when getDiagnostics shows type errors you want to resolve quickly.
typescript-expert
TypeScript expert for type system, generics, utility types, and strict mode patterns.