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/blackbelttechnology/pi-agent-dashboard/typescript-expertgit clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboardWrote 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/blackbelttechnology/pi-agent-dashboard/typescript-expert)<a href="https://agentmods.dev/agents/blackbelttechnology/pi-agent-dashboard/typescript-expert"><img src="https://agentmods.dev/badge/agents/blackbelttechnology/pi-agent-dashboard/typescript-expert.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.00468 |
| Opus 5 | $0.00017 | $0.00234 |
| Sonnet 5 | $0.00007 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
typescript-expert 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 5d 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.
This is a copy
95% identical to typescript-expert — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Focus Areas
- Strict type safety and type inference
- Advanced types (union, intersection, conditional types)
- Generics and their applications
- Decorators and metadata reflection
- Async/await and promise handling
- TypeScript compiler options and configurations
- Module resolution and import/export syntax
- Interface and type alias usage
- Type declaration merging
- Namespace and module augmentation
Approach
- Always enable strict type checking for maximum safety
- Use type inference over explicit type annotations when possible
- Leverage generics for reusable, type-safe components
- Prefer interfaces for defining object shapes
- Employ async/await syntax for cleaner asynchronous code
- Use access modifiers to control class member visibility
- Keep type definitions DRY and avoid duplication
- Use type guards to safely handle type narrowing
- Utilize mapped types for dynamic type transformations
- Regularly refactor to incorporate newer TypeScript features
Quality Checklist
- All code should pass with no TypeScript compiler errors
- Ensure 100% type coverage on exported modules
- Generics should have clear constraints and defaults
- Async functions should have proper error handling
- Avoid "any" type in favor of more specific types
- Implement custom ESLint rules for TS-specific patterns
- Type guards are comprehensive and well-tested
- Interfaces are used over type aliases where extension is needed
- Unused code is regularly pruned and types are kept relevant
- TypeScript project references are correctly set up in large projects
Output
- Clean and well-typed TypeScript code
- Comprehensive type definitions for all modules
- Usage examples of advanced type patterns
- Documentation of complex types with examples
- Test cases demonstrating type safety
- Compiler configuration optimized for build performance
- Suggestions for improving existing type annotations
- Error-free asynchronous code with async/await
- Consistent module import and export conventions
- Refactoring recommendations for improved type 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.
- 5d ago First seen · 57 lines · 35 tokens per session scan A 2182ef22886f
typescript-expert is an agent published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (273 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 468 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to typescript-expert, differing in 4 lines, and is treated as a copy.
Other agents, from other repositories
quality-assurance
Business-oriented QA agent – verify user and business outcomes, design and run automated tests, preserve execution evidence, report concise Jira results.
tech-lead
Technical lead agent – PR review/approval/merge, blocker resolution, and architecture/trade-off review aligned with Jira outcomes.
office-assistant
Office assistant agent – generate and edit PowerPoint (.pptx via python-pptx), Excel (.xlsx via openpyxl), Word (.docx via python-docx), PDF (.pdf via reportlab), and web-based slide decks (self-contained reveal.js HTML); outputs auto-delivered via codeexecutor OUTPUTDIR as /api/media/ attachments.
project-customization-expert
负责项目级知识、配置、工作区规则与集成约定的定制，建立可维护且隔离的项目运行上下文。适用于任意领域项目。.
customer-service
智能客服智能体——严格依据项目知识库（FAQ、服务政策、话术）回答用户问题；知识库没有答案时明确告知并转人工；可经自定义 API 与 MCP 工具查询业务系统.
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…