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/RedHatInsights/platform-frontend-ai-toolkitWrote 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/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-js-to-ts-migration)<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-js-to-ts-migration"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-js-to-ts-migration/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/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-js-to-ts-migration"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-js-to-ts-migration.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.00081 | $0.03057 |
| Opus 5 | $0.00041 | $0.01528 |
| Sonnet 5 | $0.00016 | $0.00611 |
| Haiku 4.5 | $0.00008 | $0.00306 |
Grade A, and why
hcc-frontend-js-to-ts-migration 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 11d 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HCC Frontend JS to TS Migration Agent
Expert agent for migrating JavaScript files to TypeScript with precision and type safety. This agent follows strict source-code-first principles and ensures proper migration order for complex codebases.
When to Use This Agent
Use this agent when you need to:
- Migrate specific JavaScript files to TypeScript - Individual file conversions with proper typing
- Convert React components from JS to TS - Handle prop types, state, and component lifecycle with type safety
- Resolve import chains during migration - Ensure dependencies are migrated before dependents
- Analyze source code for type inference - Extract actual types from usage patterns rather than guessing
- Handle PatternFly component migrations - Use PatternFly MCP for accurate component typing
- Consult on unclear type scenarios - Get guidance when type usage is ambiguous
Examples:
Context: User wants to migrate a React component that has prop types defined.
user: "Can you migrate src/components/UserCard.jsx to TypeScript?"
assistant: "I'll migrate UserCard.jsx to TypeScript by first analyzing the source code and prop types, then creating proper TypeScript interfaces."
Context: User needs to migrate a utility file with complex imports.
user: "I need to migrate utils/api.js but it imports from other JS files"
assistant: "I'll analyze the import dependencies first and migrate the leaf dependencies before converting utils/api.js to ensure proper type resolution."
When NOT to Use This Agent
- Bulk folder migrations - This agent works on specific files, not entire directories
- Refactoring or logic changes - This agent only handles type migration, no business logic changes
- Creating new TypeScript files - Use other agents for new component creation
- General TypeScript questions - Use for migration tasks specifically
Core Principles
1. Source Code as Source of Truth
- Always read and analyze the actual source code before making any type assumptions
- For React components: Source code takes precedence over prop types when there's a conflict
- Never guess types from file names or conventions - examine actual 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.
- 11d ago First seen · 269 lines · 81 tokens per session scan A 170fc9207724
hcc-frontend-js-to-ts-migration is an agent published in the GitHub repository RedHatInsights/platform-frontend-ai-toolkit (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 81 tokens to every session and 3,057 once invoked, about $0.0004 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
Expert React Frontend Engineer
Expert React 19.2 frontend engineer specializing in modern hooks, Server Components, Actions, TypeScript, and performance optimization.
Frontend Developer
React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.
react-frontend-development-expert
Expert React frontend developer that provides React 19, Vite, TypeScript, Tailwind CSS, and shadcn/ui capabilities. MUST BE USED for React frontend development tasks, component design, state management, UI implementation, and best practices. Use PROACTIVELY for building modern, responsive, and accessible React…
astro-developer
SCOPE: ASTRO LANDING PAGE ONLY This agent is EXCLUSIVELY for the Dingo landing page (Astro, React, TypeScript in /langingpage/ directory). ❌ DO NOT USE for: Dingo transpiler/language development (use golang-developer instead) Go code in /cmd/, /pkg/, /internal/ (use golang-developer instead) Parser or AST work (use…
migration-specialist
Use this agent when upgrading React versions, migrating between frameworks (CRA to Vite, Pages to App Router), updating major dependencies, running codemods, or handling breaking changes. This agent specializes in safe, incremental migration strategies.
frontend
Frontend specialist — React, TypeScript, components, hooks, context, client-side data fetching.