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/ritual-foundation/ritual-dapp-skillsWrote 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/agents/ritual-foundation/ritual-dapp-skills/ritual-dapp-debugger)<a href="https://agentmods.dev/agents/ritual-foundation/ritual-dapp-skills/ritual-dapp-debugger"><img src="https://agentmods.dev/badge/agents/ritual-foundation/ritual-dapp-skills/ritual-dapp-debugger/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/agents/ritual-foundation/ritual-dapp-skills/ritual-dapp-debugger"><img src="https://agentmods.dev/badge/agents/ritual-foundation/ritual-dapp-skills/ritual-dapp-debugger.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.00159 | $0.01629 |
| Opus 5 | $0.00079 | $0.00814 |
| Sonnet 5 | $0.00032 | $0.00326 |
| Haiku 4.5 | $0.00016 | $0.00163 |
Grade A, and why
ritual-dapp-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 12d 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.
The source is not reproduced here
Licensed BSD-3-Clause-Clear
The repository is licensed BSD-3-Clause-Clear, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 12d ago First seen · 122 lines · 159 tokens per session scan A c124b2e6baaa
ritual-dapp-debugger is an agent published in the GitHub repository ritual-foundation/ritual-dapp-skills (63 stars, last pushed 4mo ago), licensed BSD-3-Clause-Clear. It adds 159 tokens to every session and 1,629 once invoked, about $0.0008 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-30.
Other agents, from other repositories
sleuth
Smart contract bug investigator — forge traces, cast inspection, fork reproduction, revert analysis.
auth-flow-debugger
Authentication flow debugging specialist. Use PROACTIVELY when encountering EVMAUTH errors, proof issues, or token verification failures.
pipeline-architect
Use when designing a new multi-agent pipeline, generating spec/plan/tasks/topology artifacts, adding a step to an existing pipeline, updating a step, deleting a step, creating a single subagent definition, or diagnosing a pipeline topology failure.
metamask-connect-troubleshooting-specialist
Specialist for debugging MetaMask Connect SDK integration issues.
call-analysis
Analyze incoming and outgoing calls for Solidity functions using LSP call hierarchy with recursive depth tracing and manual grep for low-level calls. Use when analyzing call graphs, tracing call chains, auditing external calls, or checking reentrancy surfaces in Solidity contracts.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.