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 OpenCoven/coven --skill ritual-dapp-frontendgit clone --depth 1 https://github.com/OpenCoven/covenWrote 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/opencoven/coven/ritual-dapp-frontend)<a href="https://agentmods.dev/skills/opencoven/coven/ritual-dapp-frontend"><img src="https://agentmods.dev/badge/skills/opencoven/coven/ritual-dapp-frontend/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/opencoven/coven/ritual-dapp-frontend"><img src="https://agentmods.dev/badge/skills/opencoven/coven/ritual-dapp-frontend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 910 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00000 | $0.08209 |
| Opus 5.5 | $0.00000 | $0.03284 |
| Sonnet 5.5 | $0.00000 | $0.01642 |
| Haiku 4.5 | $0.00000 | $0.00821 |
Grade A, and why
ritual-dapp-frontend 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 1,004 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ritual dApp Frontend Skill
Version: 1.0.0
Build production-grade React/Next.js frontends for Ritual Chain dApps with async transaction state machines, on-chain event subscriptions, and wallet integration.
When to Use
Use this skill when:
- Building a frontend for a Ritual Chain dApp
- Implementing async transaction tracking UI
- Adding wallet connection for Ritual Chain
- Creating hooks for precompile interactions
- Displaying job status, fee estimates, or streaming results
- Styling transaction state indicators
Do NOT use when:
- Building backend services (use contract interaction patterns instead)
- Writing smart contracts (use Solidity tooling)
- Working with non-Ritual EVM chains (adapt chain config)
Tech Stack
| Layer | Technology | Purpose |
|---|---|---|
| Framework | Next.js 14+ (App Router) | SSR, routing, API routes |
| Chain | wagmi v2 + viem v2 | Wallet, contracts, events |
| State | Zustand v4 | Transaction state machine |
| Async | React Query v5 | Polling, caching |
| Styling | Tailwind v3 | Dark-mode-first design |
Core dependencies:
{
"next": "^14.2.0",
"wagmi": "^2.12.0",
"viem": "^2.21.0",
"@tanstack/react-query": "^5.59.0",
"zustand": "^4.5.0"
}
Quick Start Pattern
1. Setup Chain & Providers
File: lib/chain.ts
import { defineChain } from 'viem';
export const ritualChain = defineChain({
id: 1979,
name: 'Ritual',
nativeCurrency: { name: 'RIT', symbol: 'RIT', decimals: 18 },
rpcUrls: {
default: { http: ['https://rpc.ritual.network'] },
},
blockExplorers: {
default: { name: 'Ritual Explorer', url: 'https://explorer.ritual.network' },
},
});
File: lib/wagmi.ts
import { createConfig, http } from 'wagmi';
import { injected, walletConnect } from 'wagmi/connectors';
import { ritualChain } from './chain';
export const wagmiConfig = createConfig({
chains: [ritualChain],
connectors: [
injected(),
walletConnect({ projectId: process.env.NEXT_PUBLIC_WC_PROJECT_ID! }),
],
transports: {
[ritualChain.id]: http('https://rpc.ritual.network'),
},
});
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.
- 2mo ago First seen · 1,004 lines · 0 tokens per session scan A 0f0d313c9690
ritual-dapp-frontend is a skill published in the GitHub repository OpenCoven/coven (75 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 8,209 tokens. 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 skills, from other repositories
onchainkit
Build onchain apps with Coinbase's OnchainKit React components - wallets, swaps, NFTs, payments.
devtools-event-client
Create typed EventClient for a library. Define event maps with typed payloads, pluginId auto-prepend namespacing, emit()/on()/onAll()/onAllPluginEvents() API. Connection lifecycle (5 retries, 300ms), event queuing, enabled/disabled state, SSR fallbacks, singleton pattern. Unique pluginId requirement to avoid event…
walkeros-create-destination
Use when creating a new walkerOS destination to send events to a vendor or API (GA4/gtag, Meta/Facebook Pixel, Mixpanel, Amplitude, a custom HTTP API, Measurement Protocol), web or server-side. Example-driven workflow: research the vendor SDK and define step examples before implementing the destination interface, env…
walkeros-create-source
Use when creating a new walkerOS source to capture events (browser source, dataLayer interception, server/HTTP source, webhook receiver, event capture), web or server-side. Example-driven workflow: research the input format and define step examples before implementing the push interface, createTrigger, and env pattern.
openforms-mui
Author, render, preview and debug OpenForms FormSchemaJSON form definitions as idiomatic, themed, accessible MUI (React). Use when the user wants to design an OpenForms form, render an OpenForms schema with Material UI, convert an OpenForms JSON schema into a React MUI form, preview a form schema, or debug…
implementing-mcp-tools
Guide for exposing PostHog product endpoints as MCP tools. Use when creating new or updating API endpoints, adding MCP tool definitions, scaffolding YAML configs, or writing serializers with good descriptions. Covers the full pipeline from Django serializer to generated TypeScript tool handler.