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 commands/edgarbnt/reactsentinel/debug-reactgit clone --depth 1 https://github.com/edgarbnt/ReactSentinelWhat 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.00014 | $0.00205 |
| Opus 5 | $0.00007 | $0.00102 |
| Sonnet 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 yesterday.
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.
- yesterday 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 3mo ago), licensed MIT. It adds 14 tokens to every session and 205 once invoked, about $0.0001 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 commands, from other repositories
check-browser
Use Real Browser MCP to check what's currently showing in my browser.
dev-in-browser
Use your browser to view https://verso.localhost which is tied to livereload dev server which is already running. You can inspect that page (including taking screenshots!) to validate that your changes fixed the issue.
webperf
Run a web performance audit via the web-performance-auditor persona.
read
Read a specific section from an arXiv paper's HTML version (ar5iv.org).
core-review
Review code changes against SpecOps project-specific patterns. Catches recurring failure modes from real PRs — tool abstraction violations, generated file drift, cross-platform gaps, variable inconsistencies, and more. Complements full-review-gate (generic quality) and pr-fix (applying bot comments).
ship-pr
Commit all changes to a new branch, push, and open a PR for review. The original branch stays clean.