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 skills add ironbee-ai/ironbee-devtools-skills --skill react-debugginggit clone --depth 1 https://github.com/ironbee-ai/ironbee-devtools-skillsWrote 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/skills/ironbee-ai/ironbee-devtools-skills/react-debugging)<a href="https://agentmods.dev/skills/ironbee-ai/ironbee-devtools-skills/react-debugging"><img src="https://agentmods.dev/badge/skills/ironbee-ai/ironbee-devtools-skills/react-debugging/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/skills/ironbee-ai/ironbee-devtools-skills/react-debugging"><img src="https://agentmods.dev/badge/skills/ironbee-ai/ironbee-devtools-skills/react-debugging.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.00048 | $0.00986 |
| Opus 5.5 | $0.00019 | $0.00394 |
| Sonnet 5.5 | $0.00010 | $0.00197 |
| Haiku 4.5 | $0.00005 | $0.00099 |
Grade A, and why
react-debugging 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 1mo 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Debugging Skill
Debug React applications by inspecting components, props, and the component tree.
When to Use
This skill activates when:
- User is debugging a React application
- User wants to inspect React component props/state
- User needs to find which component renders an element
- User asks about React DevTools
- User mentions React Fiber or component tree
Capabilities
Component Inspection
ironbee-browser-devtools-cli react get-component-for-element --selector ".user-card"
ironbee-browser-devtools-cli --json react get-component-for-element --selector "#root > div"
Element Mapping
ironbee-browser-devtools-cli react get-element-for-component --component-name "UserCard"
ironbee-browser-devtools-cli --json react get-element-for-component --component-name "Button"
Prerequisites
Important: React tools work best with:
- Persistent Browser Context: Enable
BROWSER_PERSISTENT_ENABLE=true - React DevTools Extension: Manually install in browser profile
Without the extension, tools use best-effort DOM scanning which is less reliable.
Debugging Workflow
Find Component for Element
SESSION="--session-id react-debug"
# Navigate to React app
ironbee-browser-devtools-cli $SESSION navigation go-to --url "http://localhost:3000"
ironbee-browser-devtools-cli $SESSION sync wait-for-network-idle
# Find component for a DOM element
ironbee-browser-devtools-cli $SESSION --json react get-component-for-element \
--selector ".user-profile-card"
# Cleanup
ironbee-browser-devtools-cli session delete react-debug
Find Elements for Component
SESSION="--session-id react-debug"
# Navigate to React app
ironbee-browser-devtools-cli $SESSION navigation go-to --url "http://localhost:3000"
ironbee-browser-devtools-cli $SESSION sync wait-for-network-idle
# Find all DOM elements rendered by a component
ironbee-browser-devtools-cli $SESSION --json react get-element-for-component \
--component-name "UserCard"
# Cleanup
ironbee-browser-devtools-cli session delete react-debug
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.
- 1mo ago First seen · 140 lines · 48 tokens per session scan A e6eff989701f
react-debugging is a skill published in the GitHub repository ironbee-ai/ironbee-devtools-skills (3 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 986 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
cometchat-react-v7-troubleshooting
Diagnose a broken CometChat React v7 integration — blank panes, a collapsed/0-height surface, empty lists, no messages, the kit's error state, events that never fire, or a versionconflict. Triggers: 'cometchat react not working', 'chat is blank', 'conversations empty', 'messages not showing react', 'something went…
react
Inspect React apps and measure Web Vitals with chrome-use's built-in react … and vitals commands (component tree, props/hooks/state, re-render profiling, Suspense, LCP/CLS/INP, SPA pushstate). Requires launching with --enable react-devtools. Use when debugging a React app's renders/state or measuring page performance.
react-component-performance
Diagnoses slow React components and applies render-time fixes — re-renders, memo/useMemo/useCallback, list virtualization, Profiler traces. Not for API or database latency.
nextjs-validator
Validates Next.js 16 config and flags deprecated 14/15 patterns — proxy.ts, Turbopack, Cache Components, App Router. Use before Next.js work or when auditing a project.
react-doctor
Use when finishing a feature, fixing a bug, before committing React code, or when the user types /doctor, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canonical playbook.
react-doctor
Run after making React changes to catch issues early. Use when reviewing code, finishing a feature, or fixing bugs in a React project.