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 commands/justdvp/claude-code-templates/typescript-migrategit clone --depth 1 https://github.com/Justdvp/claude-code-templatesWhat 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.00000 | $0.00375 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
typescript-migrate 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- typescript-migrate — 100% identical, 0 lines differ
What it actually says
TypeScript Migration Assistant
Migrate $ARGUMENTS from JavaScript to TypeScript with proper typing and modern practices.
Task
I'll help you migrate JavaScript code to TypeScript by:
- Converting JavaScript files to TypeScript (.js/.jsx to .ts/.tsx)
- Adding appropriate type definitions and interfaces
- Configuring TypeScript settings for your project
- Resolving type errors and compatibility issues
- Implementing modern TypeScript patterns and features
- Ensuring backward compatibility with existing code
Process
I'll follow these steps:
- Examine your project structure and dependencies
- Analyze the JavaScript code to understand its functionality
- Create or update tsconfig.json with appropriate settings
- Convert files to TypeScript with proper type annotations
- Add necessary type definitions for libraries
- Fix type errors and implement type safety
- Refactor code to leverage TypeScript features
TypeScript Features I Can Implement
- Interfaces and type aliases for complex data structures
- Generics for reusable, type-safe components and functions
- Union and intersection types for flexible typing
- Enums for related constants
- Utility types (Partial, Pick, Omit, etc.)
- Type guards and type narrowing
- Mapped and conditional types
- Function overloading
- Readonly properties and immutability
- Module augmentation for extending third-party types
Migration Strategies
I can apply different migration approaches based on your needs:
- Gradual migration with allowJs and incremental adoption
- File-by-file conversion while maintaining functionality
- Comprehensive migration with full type safety
- Hybrid approach with .d.ts files for complex modules
- Integration with existing type definitions (@types packages)
I'll adapt to your project's specific requirements and ensure a smooth transition to TypeScript while maintaining existing functionality.
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 · 51 lines · 0 tokens per session scan A f2d374609608
typescript-migrate is a command published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 375 tokens. 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
audit-steps
Audit one or all pipelines against layout, frontmatter, topology, and runtime-safety standards — produces a severity-classified report (SEV-0/1/2/3) with cited evidence.
init-deep
Initiates a repository traversal to create localized PIPELINE-CONTEXT.md hierarchical context files.
migrate-pipeline
Migrate an existing pre-v2 per-tier pipeline (.claude/, .opencode/, .agents/codex/) into the unified data-only .superpipelines/ layout — select legacy pipeline, translate frontmatter to canonical agent defs, stage, delta-audit, gate on human approval, then atomically promote, rewrite the registry, and move the legacy…
delete-step
Delete a step from an existing pipeline — select pipeline, select step, perform gap analysis, optionally rewire, audit the delta, then gate on human approval before any deletion.
new-pipeline
Design and scaffold a new named multi-agent pipeline with git preflight, scope selection, pre-gate audit, and entry-skill generation.
new-step
Add a new step to an existing pipeline — select pipeline, choose insertion point, design component, audit the delta, then gate on human approval.