Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Initiate and manage AgentShield security audits for AI agents. Use when a user wants to audit their agent's security posture, generate cryptographic identity...
Initiate and manage AgentShield security audits for AI agents. Use when a user wants to audit their agent's security posture, generate cryptographic identity...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
The trust layer for the agent economy. Like SSL/TLS, but for AI agents. ๐ Cryptographic Identity - Ed25519 signing keys ๐ค Trust Handshake Protocol - Mutual verification before communication ๐ Public Trust Registry - Reputation scores & track records โ 77 Security Tests - Comprehensive vulnerability assessment ๐ Privacy Disclosure: See PRIVACY.md for detailed data handling information.
Agents need to communicate with other agents (API calls, data sharing, task delegation). But how do you know if another agent is trustworthy? Has it been compromised? Is it leaking data? Can you trust its responses? Without a trust layer, agent-to-agent communication is like HTTP without SSL - unsafe and unverifiable.
AgentShield provides the trust layer for agent-to-agent communication:
Ed25519 key pairs - Industry-standard cryptography Private keys stay local - Never transmitted Public key certificates - Signed by AgentShield
52 Live Attack Vectors: Prompt injection (15 variants) Encoding exploits (Base64, ROT13, Hex, Unicode) Multi-language attacks (Chinese, Russian, Arabic, Japanese, German, Korean) Social engineering (emotional appeals, authority pressure, flattery) System prompt extraction attempts 25 Static Security Checks: Input sanitization Output DLP (data leak prevention) Tool sandboxing Secret scanning Supply chain security Result: Security score (0-100) + Tier (VULNERABLE โ HARDENED)
Agent A wants to communicate with Agent B: # Step 1: Both agents get certified python3 initiate_audit.py --auto # Step 2: Agent A initiates handshake with Agent B python3 handshake.py --target agent_B_id # Step 3: Both agents sign challenges # (Automatic in v1.0.13+) # Step 4: Receive shared session key # โ Now you can communicate securely! What you get: โ Mutual verification (both agents are who they claim to be) โ Shared session key (for encrypted communication) โ Trust score boost (+5 for successful handshakes) โ Public track record (handshake history)
Searchable database of all certified agents Reputation scores based on audits, handshakes, and time Trust tiers: UNVERIFIED โ BASIC โ VERIFIED โ TRUSTED Revocation list (CRL) - Compromised agents get flagged
clawhub install agentshield cd ~/.openclaw/workspace/skills/agentshield*/
# Auto-detect agent name from IDENTITY.md/SOUL.md python3 initiate_audit.py --auto # Or manual: python3 initiate_audit.py --name "MyAgent" --platform telegram Output: โ Agent ID: agent_xxxxx โ Security Score: XX/100 โ Tier: PATTERNS_CLEAN / HARDENED / etc. โ Certificate (90-day validity)
python3 verify_peer.py agent_yyyyy
# Initiate handshake python3 handshake.py --target agent_yyyyy # Result: Shared session key for encrypted communication
Before: Agent A calls Agent B's API - no way to verify B's integrity With AgentShield: Agent A checks Agent B's certificate + handshake โ Verified communication
Before: Orchestrator spawns sub-agents - can't verify they're safe With AgentShield: All sub-agents certified โ Orchestrator knows they're trusted
Before: Download random agents from the internet - no trust guarantees With AgentShield: Browse Trust Registry โ Only hire VERIFIED agents
Before: Share sensitive data with another agent - hope it doesn't leak With AgentShield: Handshake โ Encrypted session key โ Secure data transfer
โ All 77 tests run locally - Your system prompts NEVER leave your device โ Private keys stay local - Only public keys transmitted โ Human-in-the-Loop - Explicit consent before reading IDENTITY.md/SOUL.md โ No environment scanning - Doesn't scan for API tokens What goes to the server: Public key (Ed25519) Agent name & platform Test scores (passed/failed summary) What stays local: Private key System prompts Configuration files Detailed test results
AGENTSHIELD_API=https://agentshield.live # API endpoint AGENT_NAME=MyAgent # Override auto-detection OPENCLAW_AGENT_NAME=MyAgent # OpenClaw standard
{ "agent_id": "agent_xxxxx", "public_key": "...", "security_score": 85, "tier": "PATTERNS_CLEAN", "issued_at": "2026-03-10", "expires_at": "2026-06-08" }
โ Public verification URL: agentshield.live/verify/agent_xxxxx โ Trust score (0-100) based on: Age (longer = more trust) Verification count Handshake success rate Days active โ Tier: UNVERIFIED โ BASIC โ VERIFIED โ TRUSTED
{ "handshake_id": "hs_xxxxx", "requester": "agent_A", "target": "agent_B", "status": "completed", "session_key": "...", "completed_at": "2026-03-10T20:00:00Z" }
ScriptPurposeinitiate_audit.pyRun 77 security tests & get certifiedhandshake.pyTrust handshake with another agentverify_peer.pyCheck another agent's certificateshow_certificate.pyDisplay your certificateagentshield_tester.pyStandalone test suite (advanced)
Initiate: Agent A โ Server: "I want to handshake with Agent B" Challenge: Server generates random challenges for both agents Sign: Both agents sign their challenges with private keys Verify: Server verifies signatures with public keys Complete: Server generates shared session key Trust Boost: Both agents +5 trust score
Algorithm: Ed25519 (curve25519) Key Size: 256-bit Signature: Deterministic (same message = same signature) Session Key: AES-256 compatible
Current (v1.0.13): โ 77 security tests โ Ed25519 certificates โ Trust Handshake Protocol โ Public Trust Registry โ CRL (Certificate Revocation List) Coming Soon: โณ Auto re-audit (when prompts change) โณ Negative event reporting โณ Fleet management (multi-agent dashboard) โณ Trust badges for messaging platforms
Website: https://agentshield.live GitHub: https://github.com/bartelmost/agentshield API Docs: https://agentshield.live/docs ClawHub: https://clawhub.ai/bartelmost/agentshield
AgentShield is SSL/TLS for AI agents. Get certified โ Verify others โ Establish trust handshakes โ Communicate securely. # 1. Get certified python3 initiate_audit.py --auto # 2. Handshake with another agent python3 handshake.py --target agent_xxxxx # 3. Verify others python3 verify_peer.py agent_yyyyy Building the trust layer for the agent economy. ๐ก๏ธ
During Audit Submission: { "agent_name": "YourAgent", "platform": "telegram", "public_key": "base64_encoded_ed25519_public_key", "test_results": { "score": 85, "tests_passed": 74, "tests_total": 77, "tier": "PATTERNS_CLEAN", "failed_tests": ["test_name_1", "test_name_2"] } } What is NOT sent: โ Full test output/logs โ Your prompts or system messages โ IDENTITY.md or SOUL.md file contents โ Private keys (stay in ~/.agentshield/agent.key) โ Workspace files or memory API Endpoint: Primary: https://agentshield.live/api (proxies to Heroku backend) All traffic over HTTPS (TLS 1.2+)
File Read Consent: Skill requests permission BEFORE reading IDENTITY.md/SOUL.md User sees: "Read IDENTITY.md for agent name? [Y/n]" If declined: Manual mode (--name flag) If approved: Only name/platform extracted (not full file content) Privacy-First Mode: export AGENTSHIELD_NO_AUTO_DETECT=1 python initiate_audit.py --name "MyBot" --platform "telegram" โ Zero file reads, manual input only See PRIVACY.md for complete data handling documentation.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.