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/edgarbnt/ReactSentinelWrote 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/commands/edgarbnt/reactsentinel/debug-react)<a href="https://agentmods.dev/commands/edgarbnt/reactsentinel/debug-react"><img src="https://agentmods.dev/badge/commands/edgarbnt/reactsentinel/debug-react/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/commands/edgarbnt/reactsentinel/debug-react"><img src="https://agentmods.dev/badge/commands/edgarbnt/reactsentinel/debug-react.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.00014 | $0.00205 |
| Opus 5.5 | $0.00006 | $0.00082 |
| Sonnet 5.5 | $0.00003 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
debug-react 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.
What it actually says
debug-react
Use this command when the task looks like a real browser or React runtime bug instead of a pure source-code question.
Recommended flow
- Call
get_server_infoandget_session_status. - Prefer Replay first unless the bug depends on real user state.
- Call
get_console_eventsandget_network_eventsearly. - Confirm runtime health with
get_runtime_status. - Inspect the React tree with
inspect_componentorget_react_tree. - Read runtime values with
get_component_state,get_async_timeline,get_render_hotspots, or related diagnostics. - Convert the observed failure into
validate_after_actionorvalidate_scenario.
Expected outcome
- the failing runtime path is observed, not guessed;
- the owning component or network failure is identified;
- and the investigation ends with a validation-ready scenario.
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 · 24 lines · 14 tokens per session scan A 16ddef1a5afd
debug-react is a command published in the GitHub repository edgarbnt/ReactSentinel (1 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 205 once invoked, about $0.0001 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 commands, from other repositories
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
api-aqa-flow-test-correction
Phase 7 Test Corrections of api-aqa-flow (USER APPROVAL REQUIRED).
ui-aqa-flow-test-correction
Phase 8 Test Correction of ui-aqa-flow.
brownfield-dead
Identify all dead code in the codebase: unused files and unused exports.
brownfield-score
Detailed risk scoring breakdown for a specific file. Shows all contributing factors and project comparison.