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 skills/edgarbnt/reactsentinel/react-sentinel-debugnpx skills add edgarbnt/ReactSentinel --skill react-sentinel-debuggit 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/skills/edgarbnt/reactsentinel/react-sentinel-debug)<a href="https://agentmods.dev/skills/edgarbnt/reactsentinel/react-sentinel-debug"><img src="https://agentmods.dev/badge/skills/edgarbnt/reactsentinel/react-sentinel-debug.svg" alt="Measured on agentmods" 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 | $0.00026 | $0.00296 |
| Opus 5 | $0.00013 | $0.00148 |
| Sonnet 5 | $0.00005 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
react-sentinel-debug 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 4d 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
React-Sentinel Debug Skill
Use React-Sentinel only when the task benefits from observing a live browser runtime instead of only reading repository files.
Trigger signals
- visible React UI bug;
- console error or warning tied to runtime behavior;
- failed or suspicious network request;
- render loop, hydration mismatch, or async race;
- state or prop mismatch that needs live confirmation.
Do not call React-Sentinel when
- the task is a pure refactor with no runtime symptom;
- the question is answered by documentation or static code alone;
- no runnable app or target URL exists yet;
- the user only asked for packaging, typing, or API design with no browser debugging need.
Preferred order
get_server_infoget_session_status/debug-react/reproduce-bug/validate-fix
Mode rules
- Prefer Replay by default.
- Escalate to Attach only for real user state.
- Use Shadow Sandbox only after replay already proves the bug.
- Turn the bug into
validate_after_actionorvalidate_scenarioassertions before proposing a source change. - Prefer
apply_patch_then_replayover speculative source edits when testing one runtime hypothesis.
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.
- 4d ago First seen · 40 lines · 26 tokens per session scan A 9fa42ae9e773
react-sentinel-debug is a skill published in the GitHub repository edgarbnt/ReactSentinel (1 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 296 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 skills, from other repositories
playwright-recording
Record browser interactions as video using Playwright. Use for capturing demo videos, app walkthroughs, and UI flows for Remotion videos. Triggers include recording a demo, capturing browser video, screen recording a website, or creating walkthrough footage.
kane-cli
Browser automation + AI test authoring via kane-cli - run browser objectives, generate & refine test scenarios/cases from a description, design requirement-linked test suites from a PRD/spec (assurance), parse NDJSON output, inspect logs, save runnable test.md. Use for any task requiring a real browser (navigate…
Agent Browser Automation
Fast Rust-based headless browser automation CLI with Node.js fallback for AI agents, featuring navigation, clicking, typing, snapshots, and structured commands optimized for agent workflows.
real-browser-control
Connect an AI coding agent to the user's REAL Chrome via Real Browser MCP (local MCP server + Chrome extension over localhost WebSocket). Use for live UI verification, already-open tabs, existing cookies/SSO/2FA, staging admin panels, and any task where headless Playwright or a cloud agentic browser would miss the…
browser-automation
Control the user's real logged-in Chrome via Real Browser MCP (extension + local MCP). Use for live UI checks, existing SSO/cookies, and tabs already open. Triggers: real browser, my Chrome, not headless, verify in browser. Prefer over Playwright when session state matters. Prefer Playwright for CI.
aginxbrowser
Browser engine for AI agents: fetch JS-rendered and Cloudflare-protected pages as clean markdown, run 5-engine aggregated web search (Baidu, Bing, Sogou, WeChat, Google), take screenshots as visual input, extract structured data from SPAs, and drive multi-step interactions (click, type, fill forms, login, paginate)…