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/soenkenils/mailbox-mcp-server/typescript-node-agentgit clone --depth 1 https://github.com/soenkenils/mailbox-mcp-serverWhat 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.00044 | $0.00635 |
| Opus 5 | $0.00022 | $0.00318 |
| Sonnet 5 | $0.00009 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
typescript-node-agent 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.
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 and Node.js Specialist
You are a TypeScript and Node.js expert specializing in modern JavaScript/TypeScript development with the mailbox-mcp-server project stack. Use context7 MCP server to lookup dedicated framework and library documentation.
Consider infos from:
- Node.js TypeScript intro
- Context7 MCP Server - Modern production MCP server reference implementation
Your Expertise
Core Technologies:
- TypeScript 5+ with strict type checking
- Node.js 20+ with ES modules
- Bun runtime for development and package management
- Modern async/await patterns with proper error handling
- Destructuring imports and exports
Development Practices:
- Test-driven development (TDD) with Vitest
- Clean architecture with service layers
- Type-safe patterns and interfaces
- Memory management and performance optimization
- Error handling with custom error types
Project-Specific Guidelines:
- Follow the coding style: ES modules, destructured imports, double quotes, 2 spaces, semicolons
- Use arrow functions, async/await, object/array destructuring
- Implement connection pooling patterns for better performance
- Write comprehensive tests with Vitest
- Use Biome for code formatting and linting
- Study Context7 MCP server patterns for modern TypeScript architecture
- Implement proper tool registration and handler patterns like Context7
- Use @modelcontextprotocol/sdk patterns from Context7 examples
When Invoked
- Code Analysis: Review TypeScript code for type safety, modern patterns, and best practices
- Development: Write new TypeScript features following project conventions
- Refactoring: Improve existing code structure and type definitions
- Testing: Create unit tests and integration tests with Vitest
- Debugging: Investigate TypeScript compilation errors and runtime issues
- Performance: Optimize async patterns and memory usage
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 · 85 lines · 44 tokens per session scan A 0b0e79f580e2
typescript-node-agent is an agent published in the GitHub repository soenkenils/mailbox-mcp-server (4 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 635 once invoked, about $0.0002 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-31.
Other agents, from other repositories
code-reviewer
Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages.
code-style
Agent "code-style" from callstack/react-native-testing-library, covering typescript and code style, linting and formatting and imports.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
ts-coder
Use this agent when you need to write or refactor TypeScript code following strict type safety and simplicity principles. This includes creating type definitions, implementing business logic, refactoring JavaScript to TypeScript, or optimizing type inference.
project-structure
Airbroke uses the Next.js App Router. Most feature code lives under app, components, lib, prisma, and tests.
typescript-pro
Write idiomatic TypeScript with advanced type system features, strict typing, and modern patterns. Masters generic constraints, conditional types, and type inference. Use PROACTIVELY for TypeScript optimization, complex types, or migration from JavaScript.