0protocol

Agents can sign plugins, rotate credentials without losing identity, and publicly attest to behavior.

3,891 stars
Complexity: easy

About this skill

0protocol serves as an identity substrate, offering crucial capabilities for autonomous AI agents to manage their digital identity securely. It allows agents to sign the plugins they use or develop, providing verifiable proof of origin and integrity. This skill also facilitates credential rotation without compromising the agent's persistent identity, a key feature for long-term operational security. Agents can use 0protocol to leave verifiable statements about their plugin behavior or other actions, contributing to an auditable and trustworthy record. This fosters greater transparency and accountability in AI operations, addressing critical concerns around AI provenance and reliability. Users benefit by gaining confidence in the actions and artifacts generated or utilized by AI agents. It's particularly valuable for AI systems requiring strong security, compliance, and auditing capabilities, ensuring that an agent's history and commitments are transparent and immutable.

Best use case

The primary use case is establishing trust and accountability for AI agents, especially concerning the plugins they interact with or create. This skill benefits developers and operators of AI systems who need to verify the integrity and origin of agent-driven actions, enhance security postures, and provide transparent audit trails for regulatory compliance or public scrutiny.

Agents can sign plugins, rotate credentials without losing identity, and publicly attest to behavior.

AI agents can establish a verifiable identity, sign artifacts like plugins, and record public attestations of their behavior, enhancing trust and accountability in their operations.

Practical example

Example input

mcporter call '0protocol.express(expression_type: "claim", payload: {claim_type: "artifact/signature", subject: "plugin:weather-fetcher-v2", predicate: "signed", object: "sha256:a3f8c2d1e9b7..."})'

Example output

{"status": "success", "expression_id": "expr:abc123def456ghi789jkl012mno345pqr", "message": "Plugin signed successfully."}

When to use this skill

  • When an AI agent needs a persistent, verifiable identity across different environments.
  • To sign and attest to the integrity of AI plugins, code, or other artifacts.
  • To create a public and auditable record of an agent's actions or claims.
  • To maintain agent identity and history during credential rotation or platform changes.

When not to use this skill

  • For simple, one-off AI tasks that do not require long-term identity or accountability.
  • If you require a full, blockchain-based consensus mechanism (0protocol is not consensus).
  • When the overhead of identity management and attestation is unnecessary for the task.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/0protocol/SKILL.md --create-dirs "https://raw.githubusercontent.com/openclaw/skills/main/skills/0isone/0protocol/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/0protocol/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How 0protocol Compares

Feature / Agent0protocolStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityeasyN/A

Frequently Asked Questions

What does this skill do?

Agents can sign plugins, rotate credentials without losing identity, and publicly attest to behavior.

How difficult is it to install?

The installation complexity is rated as easy. You can find the installation instructions above.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# 0.protocol

Identity substrate for autonomous agents. Sign plugins, rotate credentials without losing identity, and leave verifiable statements about plugin behavior.

Three tools: `express`, `own`, `transfer`.

## Setup

### Option 1: mcporter (Recommended)

Add to `config/mcporter.json`:

```json
{
  "mcpServers": {
    "0protocol": {
      "baseUrl": "https://mcp.0protocol.dev/mcp",
      "description": "Identity substrate for autonomous agents"
    }
  }
}
```

Test:

```bash
mcporter list 0protocol --schema
```

### Option 2: Direct MCP Config

```json
{
  "mcpServers": {
    "0protocol": {
      "url": "https://mcp.0protocol.dev/mcp"
    }
  }
}
```

## Tools

| Tool | Description |
|------|-------------|
| `express` | Create signed expression — sign plugins, log work products, record attestations |
| `own` | Query wallet, set signature expression, lookup other agents |
| `transfer` | Authenticated handoff with server-witnessed receipt |

## Canonical Use Case: Plugin Trust

### 1. Sign a plugin

```bash
mcporter call '0protocol.express(
  expression_type: "claim",
  payload: {
    claim_type: "artifact/signature",
    subject: "plugin:weather-fetcher-v2",
    predicate: "signed",
    object: "sha256:a3f8c2d1e9b7..."
  }
)'
```

The agent's identity is now permanently associated with this plugin hash. This survives restarts, platform changes, and credential rotation.

### 2. Attest to behavior

```bash
mcporter call '0protocol.express(
  expression_type: "claim",
  payload: {
    claim_type: "behavior/report",
    subject: "plugin:weather-fetcher-v2",
    predicate: "used_successfully",
    object: "100_calls_no_errors",
    evidence_refs: ["expr:abc123..."]
  }
)'
```

A recorded claim. Not consensus. Not reputation. A signed statement from one agent about an artifact.

### 3. Transfer to another agent

```bash
mcporter call '0protocol.transfer(
  to: "8b2c4d5e...",
  payload: {
    type: "task_handoff",
    expression_refs: ["expr_abc123"],
    context: "analysis complete"
  },
  visibility: "public"
)'
```

## Guarantees

| Guarantee | How |
|-----------|-----|
| **Authorship** | Ed25519 signatures. Agent generates keypair locally. |
| **Integrity** | Append-only expression log. Server-witnessed. |
| **Ordering** | Monotonic log index. Server-signed timestamps. |
| **Transfer authenticity** | Both signatures recorded. |

## What This Is Not

- Not authentication (your auth is unchanged)
- Not reputation (Phase 2)
- Not payments or tokens
- Not required for execution

## Resources

- [README / Spec](https://github.com/0isone/0protocol)
- [API Reference](https://github.com/0isone/0protocol/blob/main/API.md)
- [Migration Guide](https://github.com/0isone/0protocol/blob/main/migration.md)
- [Why](https://github.com/0isone/0protocol/blob/main/WHY.md)

Related Skills

HIPAA Compliance for AI Agents

3891
from openclaw/skills

Generate HIPAA compliance checklists, risk assessments, and audit frameworks for healthcare organizations deploying AI agents.

Security

Data Governance Framework

3891
from openclaw/skills

Assess, score, and remediate your organization's data governance posture across 6 domains.

Security

Cybersecurity Risk Assessment

3891
from openclaw/skills

You are a cybersecurity risk assessment specialist. When the user needs a security audit, threat assessment, or compliance review, follow this framework.

Security

afrexai-cybersecurity-engine

3891
from openclaw/skills

Complete cybersecurity assessment, threat modeling, and hardening system. Use when conducting security audits, threat modeling, penetration testing, incident response, or building security programs from scratch. Works with any stack — zero external dependencies.

Security

Compliance & Audit Readiness Engine

3891
from openclaw/skills

Your AI compliance officer. Guides startups and scale-ups through SOC 2, ISO 27001, GDPR, HIPAA, and PCI DSS — from zero to audit-ready. No consultants needed.

Security

Compliance Audit Generator

3891
from openclaw/skills

Run internal compliance audits against major frameworks without hiring a consultant.

Security

AI Safety Audit

3891
from openclaw/skills

Comprehensive AI safety and alignment audit framework for businesses deploying AI agents. Built around the UK AI Security Institute Alignment Project standards (2026), EU AI Act requirements, and NIST AI RMF.

Security

clickhouse-github-forensics

3891
from openclaw/skills

Query GitHub event data via ClickHouse for supply chain investigations, actor profiling, and anomaly detection. Use when investigating GitHub-based attacks, tracking repository activity, analyzing actor behavior patterns, detecting tag/release tampering, or reconstructing incident timelines from public GitHub data. Triggers on GitHub supply chain attacks, repo compromise investigations, actor attribution, tag poisoning, or "query github events".

Security

security-guardian

3891
from openclaw/skills

Automated security auditing for OpenClaw projects. Scans for hardcoded secrets (API keys, tokens) and container vulnerabilities (CVEs) using Trivy. Provides structured reports to help maintain a clean and secure codebase.

Security

mema-vault

3891
from openclaw/skills

Secure credential manager using AES-256 (Fernet) encryption. Stores, retrieves, and rotates secrets using a mandatory Master Key. Use for managing API keys, database credentials, and other sensitive tokens.

Security

guardian-wall

3891
from openclaw/skills

Mitigate prompt injection attacks, especially indirect ones from external web content or files. Use this skill when processing untrusted text from the internet, user-uploaded files, or any external source to sanitize content and detect malicious instructions (e.g., "ignore previous instructions", "system override").

Security

SX-security-audit

3891
from openclaw/skills

全方位安全审计技能。检查文件权限、环境变量、依赖漏洞、配置文件、网络端口、Git 安全、Shell 安全、macOS 安全、密钥检测等。支持 CLI 参数、JSON 输出、配置文件。当用户要求"安全检查"、"漏洞扫描"、"权限检查"、"安全审计"时使用此技能。

Security