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 skills/dork-labs/dorkos/debugging-typescript-errorsnpx skills add dork-labs/dorkos --skill debugging-typescript-errorsgit clone --depth 1 https://github.com/dork-labs/dorkosWhat 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.00039 | $0.00399 |
| Opus 5 | $0.00019 | $0.00199 |
| Sonnet 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 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.
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.
- 2d 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 (9 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 399 once invoked, about $0.0002 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 skills, from other repositories
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
perf-code-paths
Use when mapping code paths, entrypoints, and likely hot files before profiling.
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
repo-genome
7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.
review
Validate plans, execution, or PRs against wish criteria — returns SHIP / FIX-FIRST / BLOCKED with severity-tagged gaps.