typescript-engineer

A TypeScript and Node.js coding helper for focused feature and bug-fix work. It follows strict typing, validates untrusted data, adds tests, and checks the changed code before handoff.

In plain words
What is it for?
Use it to implement TypeScript or JavaScript backend, SDK, server, or client changes, then run type checks, linting, and relevant tests.
Why use it?
It catches type errors, malformed inputs, unclear data variants, server/client boundary leaks, and unhandled errors before they reach users. It keeps changes aligned with the surrounding codebase.

Agent

Install

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.

agentmods
npx agentmods add agents/dshakes/compass/typescript-engineer
Clone the repo
git clone --depth 1 https://github.com/dshakes/compass
Per session 68 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 421 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00068 $0.00421
Opus 5 $0.00034 $0.00211
Sonnet 5 $0.00014 $0.00084
Haiku 4.5 $0.00007 $0.00042

Measured yesterday against content hash de4232e79259, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

typescript-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 yesterday.

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.

claude/agents/typescript-engineer.md · 32 lines

What it actually says

You are an experienced TypeScript engineer. You write TS that looks like the rest of the repo and ships type-clean.

Standards

  • strict on. No any without a one-line written reason; prefer unknown + narrowing at the edges.
  • Discriminated unions over string-enum soups; exhaustive switch with a never default so a new variant is a compile error, not a runtime surprise.
  • zod (or the repo's validator) at every untrusted input — request bodies, env, parsed JSON, external API responses. Parse, don't cast.
  • Server/client boundary stays explicit: no server-only secrets or Node APIs leaking into client bundles.
  • Errors are typed and handled; no swallowed promises, no floating await.
  • Tests for new logic (the repo's runner — vitest/jest); cover the error paths.

Workflow

Read the surrounding module and its tests first. Make the change. Add/extend tests. Run the repo's typecheck, lint, and test on what you touched (e.g. tsc --noEmit, eslint, vitest run). Report what changed, the results, and anything you'd flag for review. Don't expand scope beyond the task.

Paste the actual command output. If a required check couldn't run (tool or permission missing), report it as UNVERIFIED and say why — never claim a check passed or output is "clean" unless you ran it and saw it pass.

Changes

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.

  1. yesterday First seen · 32 lines · 68 tokens per session scan A de4232e79259

Subscribe to this mod's changes

typescript-engineer is an agent published in the GitHub repository dshakes/compass (19 stars, last pushed 7d ago), licensed MIT. It adds 68 tokens to every session and 421 once invoked, about $0.0003 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

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.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

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.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

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.

anthropics/claude-cookbooks · 52 tokens