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/DmitriyYukhanov/claude-pluginsWrote 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/commands/dmitriyyukhanov/claude-plugins/typescript-dev)<a href="https://agentmods.dev/commands/dmitriyyukhanov/claude-plugins/typescript-dev"><img src="https://agentmods.dev/badge/commands/dmitriyyukhanov/claude-plugins/typescript-dev/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/commands/dmitriyyukhanov/claude-plugins/typescript-dev"><img src="https://agentmods.dev/badge/commands/dmitriyyukhanov/claude-plugins/typescript-dev.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.00018 | $0.00548 |
| Opus 5.5 | $0.00007 | $0.00219 |
| Sonnet 5.5 | $0.00004 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
typescript-dev 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Development Workflow
You are orchestrating a complete TypeScript development workflow. Follow these phases systematically.
Phase 1: Discovery
First, understand the project and task:
-
Check for TypeScript project markers:
tsconfig.jsonpackage.json.ts,.tsxfiles- Framework config files (next.config.js, vite.config.ts, etc.)
-
Read existing architecture:
- Check for
CLAUDE.mdor project documentation - Look at existing code patterns in
src/ - Identify framework (React, Vue, Angular, Node.js, etc.)
- Check for
-
Clarify requirements if task is ambiguous using AskUserQuestion
Phase 2: Architecture
Use the typescript-architect skill knowledge to:
- Design module structure - Interfaces, types, module boundaries
- Create test stubs - Jest/Vitest test cases
- Generate Mermaid diagrams - Class, data flow diagrams
- Define contracts - Interfaces before implementations
Present the architecture to the user for approval before implementing.
Phase 3: Implementation
Use the typescript-coder skill knowledge to implement:
- Follow TypeScript coding guidelines precisely
- Implement against the test stubs created in Phase 2
- Run tests continuously as you implement
- Use strict types (avoid
any)
Phase 4: Review
Spawn the typescript-reviewer agent to perform TypeScript-specific code review:
- Type safety issues
- Async pattern problems
- React/Framework patterns (if applicable)
- Performance red flags
- Accessibility issues
Phase 5: Testing
Use the typescript-testing skill knowledge to:
- Ensure unit tests pass
- Ensure integration tests pass
- Generate coverage report for critical paths if requested
Workflow Commands
You can run individual phases:
- "architect only" - Just Phase 2
- "implement only" - Just Phase 3 (requires existing architecture)
- "review only" - Just Phase 4
- "test only" - Just Phase 5
Usage Examples
/typescript-dev Add user authentication with JWT
/typescript-dev Implement REST API with Express
/typescript-dev Create React component library
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 · 85 lines · 18 tokens per session scan A b68f298339a4
typescript-dev is a command published in the GitHub repository DmitriyYukhanov/claude-plugins (8 stars, last pushed 7d ago), licensed MIT. It adds 18 tokens to every session and 548 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-31.
Other commands, from other repositories
rust-critique
Deep code critique — read the target Rust code and apply the full review process. Evaluates soundness, ownership, error handling, type design, async correctness, performance, and architecture. Think like a senior Rust engineer giving honest feedback.
build
Sequence decide → build → hand back for any feature or fix. Triage the change, run design-tree in plan mode (with you as the approval gate — skipped when /sonu:factory routes a ticket whose spec you already approved), build test-first under code-standards, then surface the riskiest parts before handing back to…
validate
Mechanically validate the sonu plugin repo before a PR — manifest sync, YAML frontmatter, shell-fence syntax, named-source and AI-attribution scans, cross-reference integrity, skill reachability. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
dotnet-structure
Analyze and recommend .NET backend solution and folder structure improvements. Checks projects, layers, oversized files, and boundary clarity.
svelte:component
Create new Svelte components with best practices, proper structure, and optional TypeScript support.
web-design
Design and build a complete website or webapp from a project brief — end-to-end workflow from design to working React/Vite code.