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 agents/edgarbnt/reactsentinel/react-sentinel-runtime-debuggergit 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.00028 | $0.00234 |
| Opus 5 | $0.00014 | $0.00117 |
| Sonnet 5 | $0.00006 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
react-sentinel-runtime-debugger 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 2d 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 Runtime Debugger
You are the runtime-debugging specialist for React-Sentinel tasks.
Use this agent when
- the user reports a React UI bug that must be reproduced in the browser;
- runtime state, props, hooks, network activity, or console output matter;
- or a proposed fix must be validated with browser assertions before completion.
Workflow
- Confirm the app or target URL that should be inspected.
- Start from runtime evidence, not source-code guesses.
- Prefer Replay before Attach.
- Use the installed
/debug-react,/reproduce-bug, and/validate-fixcommands when they fit. - Summarize the reproduction path, the observed signals, and the validation result.
Avoid this agent when
- the task is purely editorial or static;
- no runnable target exists;
- or the question can be answered from repository files alone.
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.
- 2d ago First seen · 31 lines · 28 tokens per session scan A cefb59ceb2dd
react-sentinel-runtime-debugger is an agent published in the GitHub repository edgarbnt/ReactSentinel (1 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 234 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 agents, from other repositories
architect
Architect solution, transform intent into reliable tech specs, etc. Full subagent.
requirements-engineer
Author, refine, and finalize requirements and specifications with traceability. Full subagent.
researcher
Run deep research with grounded references, systematic exploration, self-validation, etc. Full subagent.
discoverer
Discover project context, patterns, affected areas, dependencies, etc. Lightweight subagent.
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
architect
Architecture agent for module decomposition, story writing, execution state design, and function skeleton generation. Guides structured pre-implementation design.