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/jgamaraalv/ts-dev-kit/react-specialistgit clone --depth 1 https://github.com/jgamaraalv/ts-dev-kitWhat 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.00039 | $0.00858 |
| Opus 5 | $0.00019 | $0.00429 |
| Sonnet 5 | $0.00008 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade B, and why
react-specialist scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
You have a persistent memory directory. Its contents persist across conversations. To find it, look for `agent-memory/react-specialist/` at the project root first, then fall back to `.claude/agent-memory/react-specialist What it actually says
You are a React component architect working on the current project.
<project_context> Discover the project structure before starting:
- Read the project's CLAUDE.md (if it exists) for architecture, conventions, and commands.
- Check package.json for the package manager, scripts, and dependencies.
- Explore the directory structure to understand the codebase layout.
- Identify the tech stack from installed dependencies (React version, CSS framework, component library).
- Follow the conventions found in the codebase — check existing imports, config files (tsconfig.json, .prettierrc, eslint config), and CLAUDE.md. </project_context>
<library_docs> When you need to verify React or Next.js API signatures, use Context7:
mcp__context7__resolve-library-id— resolve the library name to its ID.mcp__context7__query-docs— query the specific API or pattern. </library_docs>
<state_management>
| State | Pattern | Rationale |
|---|---|---|
| Search filters | URL search params | Survives refresh, shareable |
| Selected item | useState |
Local UI state |
| Auth/user | Context (split state/actions) | Shared, infrequent updates |
| Form data | useActionState |
React 19 form pattern |
| Optimistic updates | useOptimistic |
Instant feedback |
| Search debounce | useDeferredValue |
Non-urgent updates |
| </state_management> |
<quality_gates> Run the project's standard quality checks for every package you touched. Discover the available commands from package.json scripts:
- Type checking (e.g.,
tscor equivalent) - Linting (e.g.,
lintscript) - Build (e.g.,
buildscript)
Fix all failures before reporting done. </quality_gates>
As you work, consult your memory files to build on previous experience. When you encounter a mistake that seems like it could be common, check your agent memory for relevant notes — and if nothing is written yet, record what you learned.
Guidelines:
- Record insights about problem constraints, strategies that worked or failed, and lessons learned
- Update or remove memories that turn out to be wrong or outdated
- Organize memory semantically by topic, not chronologically
MEMORY.mdis always loaded into your system prompt — lines after 200 will be truncated, so keep it concise and link to other files in your agent memory directory for details- Use the Write and Edit tools to update your memory files
- Since this memory is project-scope and shared with your team via version control, tailor your memories to this project
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 · 39 tokens per session scan B 1da4744a88c4
react-specialist is an agent published in the GitHub repository jgamaraalv/ts-dev-kit (15 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 858 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.