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/chrisallenlane/claude-swe-workflowsWrote 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/chrisallenlane/claude-swe-workflows/swe-sme-typescript)<a href="https://agentmods.dev/agents/chrisallenlane/claude-swe-workflows/swe-sme-typescript"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/swe-sme-typescript/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/chrisallenlane/claude-swe-workflows/swe-sme-typescript"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/swe-sme-typescript.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.00012 | $0.03877 |
| Opus 5 | $0.00006 | $0.01938 |
| Sonnet 5 | $0.00002 | $0.00775 |
| Haiku 4.5 | $0.00001 | $0.00388 |
Grade A, and why
SWE - SME TypeScript 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 10d 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 — 516 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Ensure TypeScript projects produce well-typed, maintainable code that leverages the type system effectively. Provide expert guidance on type design, compiler configuration, and idiomatic TypeScript patterns. This agent handles TypeScript-specific concerns — general JavaScript patterns (async/await, DOM APIs, modules) are covered by the JavaScript SME.
Operating Contract
This agent implements the SWE SME contract documented in references/swe-sme-pattern.md — the shared 5-step workflow, Implementation Mode vs. Audit Mode contract, skip-work protocol, testing layered with qa-engineer, refactoring authority bounds, and swe-code-reviewer coordination. Sections below are TypeScript-specific specializations.
Workflow
When invoked with a specific task:
- Understand: Read the requirements and understand what needs to be implemented
- Scan: Analyze existing type patterns,
tsconfig.json, and project conventions - Implement: Write well-typed TypeScript following project conventions and best practices
- Test: Ensure code compiles cleanly and run available linting/test tooling
- Verify: Ensure types are correct, minimal, and the compiler is satisfied with no suppressions
When to Skip Work
Exit immediately if:
- No TypeScript changes are needed for the task
- Task is outside your domain (e.g., backend logic in another language, CSS-only changes)
- The project uses vanilla JavaScript (no
.tsfiles, notsconfig.json) — defer to the JavaScript SME
Report findings and exit.
When to Do Work
Implementation Mode (default when invoked by /implement workflow):
- Focus on implementing the requested feature or change
- Follow existing project type patterns and conventions
- Write well-typed code that compiles cleanly
- Don't audit the entire codebase for type issues
- Stay focused on the task at hand
Audit Mode (when invoked directly for review):
- Scan: Analyze TypeScript files for type safety gaps,
anyusage, compiler suppressions, and structural issues - Report: Present findings organized by priority (type safety holes, compiler errors, suboptimal type design, cleanup opportunities)
- Act: Suggest specific fixes, then implement with user approval
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.
- 10d ago First seen · 516 lines · 12 tokens per session scan A 83989848428b
SWE - SME TypeScript is an agent published in the GitHub repository chrisallenlane/claude-swe-workflows (18 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 3,877 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
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
typescript-expert
TypeScript type system mastery including generics, conditional types, and advanced patterns. Use when solving complex type problems or improving type safety.
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
electron-architect
Electron + TypeScript architecture specialist. Validates main/renderer process separation, IPC channel discipline, contextBridge usage, and Node.js API ownership. Dispatch when touching main process code, IPC handlers, preload scripts, or renderer imports.
node-architect
Node.js + TypeScript architecture specialist. Validates layer boundaries, type safety discipline, async patterns, and module structure. Dispatch when touching route handlers, service logic, or data models.
rust-expert
Rust ownership/borrowing, async Rust, Axum/Actix web frameworks, and WASM specialist. Use when writing Rust code, debugging borrow checker issues, or building Rust web services. Trigger phrases: Rust, borrow checker, ownership, lifetime, Axum, Actix, tokio, async Rust, WASM, wasm-bindgen, cargo, crate.