data

A data-inspection command for checking SQLite tables and state files used by DorkOS. SQLite is a file-based database, while state files store configuration and runtime information as JSON.

In plain words
What is it for?
Use it to inspect database tables, run SQL queries, check relay adapters and sessions, review message queues, and verify schedules or agent records.
Why use it?
It lets you verify what the application actually stored when data is missing, incorrect, or not appearing in the interface.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/dork-labs/dorkos/data
Clone the repo
git clone --depth 1 https://github.com/dork-labs/dorkos

Made for: Claude Code.

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,718 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00009 $0.02718
Opus 5 $0.00005 $0.01359
Sonnet 5 $0.00002 $0.00544
Haiku 4.5 $0.00001 $0.00272

Measured 2d ago against content hash a3b2465d6507, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

data 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.

.claude/commands/debug/data.md · 352 lines

How it starts

The opening of the file, as written. The whole thing — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Data Debugging

Inspect and verify database state and subsystem data files directly. Use this command to:

  • View SQLite database tables and data
  • Inspect relay state files (adapters, bindings, sessions, mailboxes)
  • Debug "data not showing" issues
  • Verify pulse schedule and run state
  • Check mesh agent registry

Data Architecture

DorkOS stores data in the .dork directory:

{DORK_HOME}/
├── config.json              # Server configuration
├── dork.db                  # SQLite database (WAL mode)
├── logs/
│   └── dorkos.log           # NDJSON structured logs
└── relay/
    ├── adapters.json         # Adapter configurations
    ├── bindings.json         # Adapter-agent bindings
    ├── sessions.json         # Active session mappings
    ├── access-rules.json     # Access control rules
    └── mailboxes/            # Per-subject message files
        └── relay.*.json      # Message queues by subject

DORK_HOME Location

Environment Location
Development apps/server/.temp/.dork/
Production ~/.dork/ (or DORK_HOME env var)

Arguments

Parse $ARGUMENTS:

  • If a table name is provided, query that SQLite table
  • If a SQL query is provided, execute it
  • If --relay flag, inspect relay state files
  • If --pulse flag, inspect pulse schedules and runs
  • If --mesh flag, inspect mesh agent registry
  • If empty, show overview and prompt for action

Phase 1: Data Overview

1.1 Show Available Data Sources

DORK_HOME="apps/server/.temp/.dork"

echo "=== Config ==="
cat "$DORK_HOME/config.json" | python3 -m json.tool

echo "=== SQLite Tables ==="
sqlite3 "$DORK_HOME/dork.db" ".tables"

echo "=== Relay State Files ==="
ls -la "$DORK_HOME/relay/" 2>/dev/null

echo "=== Log Files ==="
ls -la "$DORK_HOME/logs/" 2>/dev/null

1.2 Determine Action

AskUserQuestion:
  question: "What would you like to inspect?"
  header: "Action"
  options:
    - label: "SQLite database"
      description: "Query pulse, relay, or mesh tables in dork.db"
    - label: "Relay state files"
      description: "Inspect adapters, bindings, sessions, mailboxes"
    - label: "Server configuration"
      description: "View config.json settings"
    - label: "Run a custom query"
      description: "Execute a specific SQL query"

Read the full file on GitHub · 352 lines

Changes

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.

  1. 2d ago First seen · 352 lines · 9 tokens per session scan A a3b2465d6507

Subscribe to this mod's changes

data is a command published in the GitHub repository dork-labs/dorkos (9 stars, last pushed 2d ago), licensed MIT. It adds 9 tokens to every session and 2,718 once invoked, about $0.0000 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.