Darkmatter

v2.0.0

Commit agent context to DarkMatter, pull verified context from upstream agents, replay decision chains, fork from checkpoints, and verify chain integrity. Us...

0· 140·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for bengunvl/darkmatter.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Darkmatter" (bengunvl/darkmatter) from ClawHub.
Skill page: https://clawhub.ai/bengunvl/darkmatter
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: DARKMATTER_API_KEY
Required binaries: curl
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install darkmatter

ClawHub CLI

Package manager switcher

npx clawhub@latest install darkmatter
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the declared behavior: the SKILL.md exclusively documents HTTP calls to https://darkmatterhub.ai for commit/pull/replay/fork/verify/export operations. The single required env var (DARKMATTER_API_KEY) and required binary (curl) are appropriate and expected for that purpose.
Instruction Scope
The instructions explicitly send agent context to darkmatterhub.ai (and include a prominent data notice). This is coherent with the stated purpose, but it does mean the skill will transmit potentially sensitive agent context to an external service; the SKILL.md does not attempt to read local files or other env vars beyond the declared API key.
Install Mechanism
No install spec and no code files — instruction-only. Nothing is written to disk by the skill itself; runtime usage relies on curl being present. This minimizes installer-related risk.
Credentials
Only one required environment variable (DARKMATTER_API_KEY) is declared and used as the Authorization bearer token in API calls. That single credential is proportionate to the documented API usage. No unrelated secrets, config paths, or additional credentials are requested.
Persistence & Privilege
The skill is not marked always:true and does not request persistent system modifications. It can be invoked autonomously per platform defaults, which is expected for skills of this nature.
Assessment
This skill will transmit your agent's context/output to an external service (darkmatterhub.ai) using the DARKMATTER_API_KEY. If you install it, consider: (1) only provide a key with the minimum necessary permissions and be prepared to rotate/revoke it if needed; (2) avoid committing secrets or sensitive PII in payloads sent to the service; (3) review the service's privacy/security policy and the linked GitHub repo if you plan to trust it with production data; (4) test with non-sensitive data first; and (5) if you require full control over your data, consider self-hosting the open-source DarkMatter server referenced in the SKILL.md.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🌑 Clawdis
Binscurl
EnvDARKMATTER_API_KEY
Primary envDARKMATTER_API_KEY
latestvk9705z5ycmbzdex4ska7k5484h83gnkd
140downloads
0stars
2versions
Updated 1mo ago
v2.0.0
MIT-0

DarkMatter — Execution Lineage for AI Agents

DarkMatter is the execution history layer for multi-agent systems. Every agent action becomes an immutable, cryptographically chained context commit — replayable, forkable, and independently verifiable.

Base URL: https://darkmatterhub.ai API key env: DARKMATTER_API_KEY Get a key: https://darkmatterhub.ai/signup Live demo: https://darkmatterhub.ai/demo

Data notice: This skill sends agent context to darkmatterhub.ai. DarkMatter is open source (MIT) and fully self-hostable: https://github.com/darkmatter-hub/darkmatter


When to use this skill

Use when the user asks to:

  • Commit context or results to DarkMatter for another agent
  • Pull or inherit context from an upstream agent
  • Replay a full decision chain (root to tip)
  • Fork execution from a checkpoint
  • Verify chain integrity
  • Export an audit artifact
  • Check agent identity

Commands

1. Commit context to another agent

curl -s -X POST https://darkmatterhub.ai/api/commit \
  -H "Authorization: Bearer $DARKMATTER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "toAgentId": "<RECIPIENT_AGENT_ID>",
    "payload": {
      "input":  "<what this agent received>",
      "output": "<what this agent produced>",
      "memory": {}
    },
    "agent": {
      "role":     "<researcher|writer|reviewer>",
      "provider": "<anthropic|openai|local>",
      "model":    "<model name>"
    },
    "parentId":  "<parent ctx_id if chaining>",
    "traceId":   "<optional trace group>",
    "eventType": "commit"
  }'

Response is a canonical v2 context object. Use id as parentId in the next commit to build the lineage chain.


2. Pull verified context (inherit from upstream)

curl -s https://darkmatterhub.ai/api/pull \
  -H "Authorization: Bearer $DARKMATTER_API_KEY"

Returns all verified contexts addressed to this agent, newest first.


3. Replay full decision chain

curl -s "https://darkmatterhub.ai/api/replay/<CTX_ID>" \
  -H "Authorization: Bearer $DARKMATTER_API_KEY"

# Summary mode (no payloads, faster):
curl -s "https://darkmatterhub.ai/api/replay/<CTX_ID>?mode=summary" \
  -H "Authorization: Bearer $DARKMATTER_API_KEY"

Returns ordered chain root to tip with every payload, agent attribution, per-step integrity verification, and chainIntact boolean.


4. Fork from a checkpoint

curl -s -X POST https://darkmatterhub.ai/api/fork/<CTX_ID> \
  -H "Authorization: Bearer $DARKMATTER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"fromCheckpoint": "<ctx_id>", "branchKey": "experiment-1"}'

Returns new context ID with fork_of, fork_point, lineage_root. Continue by committing with parentId set to the new ID. Original chain is never modified.


5. Verify chain integrity

curl -s "https://darkmatterhub.ai/api/verify/<CTX_ID>" \
  -H "Authorization: Bearer $DARKMATTER_API_KEY"

Returns: chain_intact, length, root_hash, tip_hash, broken_at, fork_points.


6. Export portable audit artifact

curl -s "https://darkmatterhub.ai/api/export/<CTX_ID>" \
  -H "Authorization: Bearer $DARKMATTER_API_KEY" \
  -o "darkmatter_ctx.json"

Downloads JSON with full chain, integrity proof, chain_hash (stable), and export_hash (unique per export instance).


7. Check agent identity

curl -s https://darkmatterhub.ai/api/me \
  -H "Authorization: Bearer $DARKMATTER_API_KEY"

Event types

Developer: commit, fork, revert, branch, merge, spawn, timeout, retry, checkpoint, error Compliance: override, consent, escalate, redact, audit

Set via eventType field in commit. Defaults to commit.


Integrity model

Each commit: payload_hash = sha256(payload), integrity_hash = sha256(payload_hash + parent_integrity_hash). Tampering at any node breaks every downstream hash. Broken chain policy: permissive — commits still allowed but flagged. Fork from last valid node to start a clean branch.


Key rules

  • Always pass parentId when chaining commits — this builds the lineage graph
  • Context IDs are globally unique: ctx_{timestamp}_{hex}
  • Forked branches carry fork_of, fork_point, lineage_root
  • chain_hash in exports is deterministic — same chain = same hash
  • Legacy context field still accepted (stored as { output: context })

Comments

Loading comments...