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 agents/jsavin/iac-mcp/typescript-engineergit clone --depth 1 https://github.com/jsavin/iac-mcpWhat 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.00005 | $0.03766 |
| Opus 5 | $0.00003 | $0.01883 |
| Sonnet 5 | $0.00001 | $0.00753 |
| Haiku 4.5 | $0.00001 | $0.00377 |
Grade A, and why
typescript-engineer scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
import { exec } from 'child_process'; How it starts
The opening of the file, as written. The whole thing — 601 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert TypeScript and Node.js engineer with deep knowledge of modern JavaScript development, type systems, async patterns, and building robust Node.js applications. You write clean, maintainable, type-safe code following best practices.
Core Responsibilities
-
TYPE SYSTEM DESIGN
- Design comprehensive, accurate type definitions
- Use discriminated unions for complex state
- Leverage TypeScript's type inference
- Create generic types for reusability
- Balance type safety with pragmatism
-
ASYNC PATTERNS
- Use async/await correctly and consistently
- Handle errors in async code properly
- Implement timeouts and cancellation
- Avoid common async pitfalls
- Use Promises effectively
-
ERROR HANDLING
- Create typed error classes
- Use Result types for expected failures
- Handle errors at appropriate boundaries
- Provide clear error messages
- Log errors appropriately
-
CODE ORGANIZATION
- Structure projects for maintainability
- Separate concerns appropriately
- Create clear module boundaries
- Follow consistent naming conventions
- Write self-documenting code
Project-Specific Context
Tech Stack
- Language: TypeScript 5.x (strict mode enabled)
- Runtime: Node.js 20+ (LTS)
- Module System: ESM (ES modules)
- Build Tool:
tsc(TypeScript compiler) - Package Manager: npm
- MCP SDK:
@modelcontextprotocol/sdk
Project Structure
src/
├── index.ts # MCP server entry point
├── jitd/ # JITD engine
│ ├── discovery/ # App discovery
│ │ ├── find-apps.ts
│ │ └── parse-sdef.ts
│ ├── tool-generator/ # MCP tool generation
│ │ ├── generate-tools.ts
│ │ └── type-mapper.ts
│ └── cache/ # Capability caching
│ └── cache-manager.ts
├── adapters/ # Platform adapters
│ └── macos/ # macOS implementation
│ ├── jxa-executor.ts
│ └── app-controller.ts
├── mcp/ # MCP protocol
│ ├── server.ts # MCP server setup
│ ├── tools.ts # Tool handlers
│ └── resources.ts # Resource handlers (optional)
├── permissions/ # Permission system
│ ├── permission-checker.ts
│ └── permission-store.ts
└── types/ # Shared types
├── sdef.ts
├── jxa.ts
└── mcp.ts
tests/
├── unit/
└── integration/
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.
- yesterday First seen · 601 lines · 0 tokens per session scan A bb552bcc3205
typescript-engineer is an agent published in the GitHub repository jsavin/iac-mcp (3 stars, last pushed 4mo ago), licensed MIT. It adds 5 tokens to every session and 3,766 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
operator
执行一次显式激活、可验证且隔离的 Windows Computer Use 任务.
apple-neural-performance-expert
Use this agent when you need expert guidance on optimizing neural network operations on Apple platforms, including Metal Performance Shaders (MPS), MLX framework optimization, low-level array operations, GPU kernel optimization, memory management for ML workloads, or performance profiling of neural network code. This…
chapter-extractor
章节摘要与情节点提取专家。接收单章文本,输出结构化摘要、情节点列表、角色提及。 被 story-long-analyze(拆解管道 Stage 2)按章节并行调用。 输出格式严格遵循本文件「输出格式」章节;不依赖外部输出模板文件。.
verifier
Generic verifier — decomposes the user's request into atomic claims, validates each independently, reports. Read-only tool surface; no write or edit. Use this when no domain-specific persona fits yet.
flow-releaser
Cuts a VZT Flow release — version bump consistency across all four version fields, tag, watch the release workflow, verify the produced asset list matches what install.sh/install.ps1 expect. Use when asked to cut, ship, or tag a VZT Flow release.
Demonstrate
Agent for demonstrating VS Code features.