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 rules/origintrail/dkg/dkg-debug-chatgit clone --depth 1 https://github.com/OriginTrail/dkgWrote 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/rules/origintrail/dkg/dkg-debug-chat)<a href="https://agentmods.dev/rules/origintrail/dkg/dkg-debug-chat"><img src="https://agentmods.dev/badge/rules/origintrail/dkg/dkg-debug-chat.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.00715 | $0.00715 |
| Opus 5 | $0.00358 | $0.00358 |
| Sonnet 5 | $0.00143 | $0.00143 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
dkg-debug-chat 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DKG agent-to-agent debug chat
The two DKG nodes in this workspace can be paired with each other. When they are, you (the Cursor agent on this node) can exchange encrypted libp2p messages with the Cursor / Claude Code / Codex agent on the other node via two MCP tools:
dkg_check_inbox— read unread peer messages from this node's local SQLite history.dkg_send_message— send an encrypted chat to another agent on the network.
When to call which
Call dkg_check_inbox at the start of every session. If the digest is non-empty, surface the messages to the operator BEFORE doing anything else — those peers are waiting for a reply. After the operator types anything, your first line should look like:
"Before I get to that —
bob-nodesent 2 messages while you were away: …"
Call dkg_check_inbox again whenever:
- The operator's prompt references another node, OR
- The current task is part of a known cross-node debugging effort, OR
- You see an injected
<dkg-inbox-notice>block in the session context (the prompt-hook may have already fetched fresh messages — re-check anyway to be sure nothing was missed).
Call dkg_send_message whenever the operator says "ask ", "tell ", "let know", "ping ", or otherwise indicates cross-node communication. Use the operator's word for the recipient as to — the daemon resolves it. Don't pause for clarification on recognisable names ("alice's agent" → to: "alice-node").
ACL-aware error handling
If dkg_send_message returns delivered: false with error: "unauthorized: ...", the receiver's chat ACL rejected the message. Don't retry — the situation is human-fixable. Tell the operator something like:
"Receiver rejected my message via their chat ACL:
<reason>. Ask the operator on the other node to either add this node to theirchat.acl.peerAllowlist, or add us as a member of the CG they have scoped to."
For any other error (peer not found, timeout, network), retry once before bothering the operator.
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 · 41 lines · 715 tokens per session scan A 99f95e7fccd9
dkg-debug-chat is a cursor rule published in the GitHub repository OriginTrail/dkg (144 stars, last pushed today), licensed Apache-2.0. It adds 715 tokens to every session, about $0.0036 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 cursor rules, from other repositories
cursor-memory
Shokunin memory system: persistent context across sessions.
System Components and Requirements
Transforms Databricks Unity Catalog tables into a materialized knowledge graph, with ontology design and reasoning exposed as tools via MCP.
gps-skin-ui
/Users/theodoreaddo/.cursor/rules/gps-skin-ui.mdc.
cursorrules
🧠 Fast, zero-dependency structured knowledge base (.agent-kb/) with 2D neural graph visualizer │ & MCP server for Claude, Codex, PI, Cursor, Windsurf, Zed & Other AI coding agents.
langgraph-best-practices
Comprehensive reference for building LangGraph agent workflows including core concepts, graph construction patterns, state management, advanced patterns like Send API and Command, and production-ready code examples.
nextjs
Cursor rule "nextjs" from devridge0/basilic-evm, covering next.js rules, core principles, key conventions, component architecture and data fetching.