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 dcp-ai-protocol/dcp-ai --skill openclawgit clone --depth 1 https://github.com/dcp-ai-protocol/dcp-aiWrote 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/dcp-ai-protocol/dcp-ai/openclaw)<a href="https://agentmods.dev/skills/dcp-ai-protocol/dcp-ai/openclaw"><img src="https://agentmods.dev/badge/skills/dcp-ai-protocol/dcp-ai/openclaw/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/dcp-ai-protocol/dcp-ai/openclaw"><img src="https://agentmods.dev/badge/skills/dcp-ai-protocol/dcp-ai/openclaw.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00022 | $0.00841 |
| Opus 5.5 | $0.00009 | $0.00336 |
| Sonnet 5.5 | $0.00004 | $0.00168 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
dcp-citizenship 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 1mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DCP Citizenship — AI Agent Governance
You have access to the Digital Citizenship Protocol (DCP) tools. These tools ensure that every action you take is declared, verified, and auditable, binding your actions to a human owner.
Setup (run once per session)
Before performing any sensitive action, set up your DCP identity:
dcp_identity_setup({
session_id: "<current session/thread id>",
owner_name: "<human owner's name>",
jurisdiction: "<ISO country code, e.g. US, ES, MX>",
capabilities: ["browse", "api_call"], // what you're allowed to do
risk_tier: "medium"
})
This generates an Ed25519 keypair, a Responsible Principal Record, and an Agent Passport.
Before every sensitive action
Always declare an intent before performing actions like:
- Web browsing, API calls, file writes, code execution, emails, payments
dcp_declare_intent({
session_id: "<session id>",
action_type: "api_call", // browse | api_call | send_email | write_file | execute_code | ...
target_channel: "api", // web | api | email | filesystem | runtime | ...
estimated_impact: "medium", // low | medium | high
data_classes: ["contact_info"] // none | pii | credentials | financial_data | ...
})
The response tells you if you can proceed:
- approve → Go ahead with the action.
- escalate → Ask the human owner for confirmation before proceeding.
- block → Do NOT proceed. Inform the user that the action is too risky.
After every action
Log the result for the audit trail:
dcp_log_action({
session_id: "<session id>",
intent_id: "<intent_id from declare_intent>",
outcome: "API returned 200 OK with user profile",
evidence_tool: "web.fetch",
evidence_result_ref: "https://api.example.com/users/123"
})
Verify external bundles
If you receive a DCP Signed Bundle from another agent, verify it:
dcp_verify_bundle({
signed_bundle: { ... }, // the full signed bundle JSON
public_key: "base64..." // optional, uses bundle's signer key if omitted
})
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- package-lock.json 79 KB
- package.json 1.4 KB
- README.md 7.1 KB
- src/__tests__/index.test.ts 13 KB runs code
- src/__tests__/intent-tier.test.ts 1.3 KB runs code
- src/index.ts 13 KB runs code
- src/state/agent-state.ts 3.7 KB runs code
- src/tools/audit.ts 7.3 KB runs code
- src/tools/delegation.ts 2.3 KB runs code
- src/tools/identity.ts 6.9 KB runs code
- src/tools/intent.ts 8.7 KB runs code
- src/tools/lifecycle.ts 6.2 KB runs code
- src/tools/succession.ts 2.2 KB runs code
- src/tools/verify.ts 7.0 KB runs code
- tsconfig.json 318 B
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.
- 1mo ago First seen · 103 lines · 22 tokens per session scan A 2f479c7f9641
dcp-citizenship is a skill published in the GitHub repository dcp-ai-protocol/dcp-ai (23 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 841 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
swarmwage-publish
Publish your agent's capabilities to the Swarmwage registry and earn USDC for each call. Lets your agent advertise services (image generation, audio transcription, charting, custom domain workflows…) on the open agent hire protocol — other AI agents discover you, hire you with one function call, and pay you in USDC on…
swarmwage-hire
Discover, inspect, dry-run, hire, and pay AI capabilities through Swarmwage. Start with wallet-free capability search and x402 reliability checks; use a dedicated USDC wallet only for real hires or paid external x402 calls.
capability-evolver
A self-evolution engine for AI agents. Analyzes runtime history to identify improvements and applies protocol-constrained evolution. Communicates with EvoMap Hub via local Proxy mailbox.
ironmesh-send
Send an application message (MSG) to a specific IronMesh peer. Use when the user asks to "send X to agent Y" or "ping peer Z". Has side effects — only invoke when the user explicitly asks.
ironmesh-audit
Tail the tamper-evident IronMesh audit log for security events. Use when investigating a TOFU mismatch, auth failure, peer dropping out, or a suspected attack.
ironmesh-peers
Drill into per-peer IronMesh metrics — retry reasons, session rekeys, offline-since, transport type. Use when ironmesh-status shows a problem on a specific peer and you need detail.