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 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/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/edgarbnt/reactsentinel/react-sentinel-debug"><img src="https://agentmods.dev/badge/skills/edgarbnt/reactsentinel/react-sentinel-debug.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.00026 | $0.00296 |
| Opus 5.5 | $0.00010 | $0.00118 |
| Sonnet 5.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 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
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.
- 1mo 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 5mo ago), licensed MIT. It adds 26 tokens to every session and 296 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 skills, from other repositories
chrome-devtools
Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance.
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
moli-webfetch
Fetch, inspect, crawl, and capture live, JavaScript-rendered websites with Moli. Use when Codex needs current web content, web research, fact lookup, link following, a bounded crawl, client-rendered or response-gated content, network diagnostics, or a standalone HTML, Markdown, JSON, semantic-tree, viewport or…
moli-cdp-server
Start Moli's CDP server and connect Playwright, Puppeteer, or raw CDP clients. Use to run a headless-browser CDP endpoint, replace a Chromium process, attach over CDP, enable real layout and screenshot surfaces, or diagnose CDP discovery, connection, and target startup—even when Moli is not named.
ego-lite-simplify
Find and implement evidence-backed simplifications in the ego-lite repository. Use when reviewing the codebase for dead code, duplicated state or APIs, speculative abstractions, unnecessary compatibility layers, hand-written infrastructure, excessive tests or documentation, or when the user asks to reduce code size or…
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.