verified-communication

Sign and axiom-verify messages between Factory agents via MessageRouter.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gitwalter/cursor-agent-factory --skill verified-communication
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verified-communication
Source: https://github.com/gitwalter/cursor-agent-factory/tree/main/.cursor/skills/verified-communication
Command: npx skills add https://github.com/gitwalter/cursor-agent-factory --skill verified-communication

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Factory agents require a trustworthy, auditable way to communicate across the agent society. This skill provides cryptographically signed, axiom-verified messaging to prevent manipulation and ensure accountability.

Core Features & Use Cases

  • Cryptographically signed messages between agents with axiom verification
  • Message routing, contracts, and governance for agent societies
  • Use Case: Orchestrator delegates a task to a worker with verified delivery and auditable traceability

Quick Start

  • Initialize a shared SocietyContext
  • Create two AgentSocietyBridge instances (e.g., orchestrator and worker)
  • Register both bridges with a MessageRouter
  • Send a verified message with a payload and axiom_alignment

Frequently Asked Questions about verified-communication

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable cryptographically signed messaging between orchestrator and worker agents?

To enable signed agent communication, initialize a shared SocietyContext and create AgentSocietyBridge instances for both orchestrator and worker, then register them with a MessageRouter to send axiom-verified payloads with auditable traceability.

What is axiom-verified communication for distributed agent systems?

Axiom-verified communication is a messaging mechanism that cryptographically signs interactions between Factory agents to prevent manipulation, ensuring contract-based governance and accountability across distributed agent societies.

How do I set up an auditable event trail for agent-to-agent task delegation?

Set up an auditable event trail by registering orchestrator and worker AgentSocietyBridge instances with a MessageRouter, allowing you to send verified messages with payload and axiom alignment for traceable task delegation.

Can I use contract-based verification for agent communication without external dependencies?

Yes, you can implement contract-based verification without external dependencies by using the built-in AgentSocietyBridge and MessageRouter components to establish axiom-aligned, signed messages across your agent society.

When do I need axiom verification for agent communication?

You need axiom verification when orchestrator-worker patterns require trustworthy, tamper-proof message routing and contract-based interactions, ensuring distributed agents remain accountable through cryptographically signed event trails.

What are the limitations of using signed messages for agent communication?

Signed agent communication requires initializing a shared SocietyContext and registering all AgentSocietyBridge instances with a MessageRouter beforehand, meaning unregistered agents cannot participate in the axiom-verified message routing or audit log.