Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Productivity
Agent Passport
OAuth for the agentic era. Consent-gating for ALL sensitive agent actions. 75+ data-driven threat definitions with auto-updates (like antivirus signatures)....
skill openclawclawhub Free
OAuth for the agentic era. Consent-gating for ALL sensitive agent actions. 75+ data-driven threat definitions with auto-updates (like antivirus signatures)....
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, TRADEMARK.md, _meta.json, agents/openai.yaml, references/mandates.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 2.4.2
Provenance
- Publisher
- markneville
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
30-Second Setup
# Initialize and register your agent ./mandate-ledger.sh init agent:my-assistant "Your Name" "personal assistant" "openclaw" # Grant dev tool access (git, npm, docker, etc.) ./mandate-ledger.sh create-from-template dev-tools # That's it! The agent will now check permissions before sensitive actions. Templates available: dev-tools ยท email-team <domain> ยท file-ops <path> ยท web-research ยท safe-browsing ยท coding ยท email-assistant ยท read-only ยท full-auto Run ./mandate-ledger.sh templates to see all options.
โก Agent Behavioral Contract
If you are an agent reading this skill, these are your rules. Follow them.
When to Check
Before performing ANY of these actions, you MUST call check-action first: ActionCategoryExample targetRunning a shell commandsystem"git pull", "npm install"Sending a message/emailcommunication"bob@company.com"Writing/deleting a filedata"/path/to/file.txt"Making an API call with side effectsexternal_api"api.github.com"Spending moneyfinancial"merchant_amazon" with amountActing publicly as the useridentity"twitter_post" You do NOT need to check: reading files, web searches, internal reasoning, or anything with no side effects.
How to Check
SCRIPT_DIR="$HOME/.openclaw/skills/agent-passport/scripts" result=$($SCRIPT_DIR/mandate-ledger.sh check-action "<your_agent_id>" "<category>" "<target>" [amount]) Parse the result: authorized: true โ proceed, then log the action afterward authorized: false โ STOP. Ask the user. If response includes kill_switch: true or reason Kill switch engaged โ STOP immediately and ask user to run mandate-ledger.sh unlock
The Flow
1. You want to do something sensitive 2. Call check-action 3. IF authorized: a. Do the thing b. Log it: mandate-ledger.sh log-action <mandate_id> <amount> "<description>" 4. IF denied: a. Tell the user what you want to do and why b. Suggest a mandate (show scope, duration, constraints) c. Wait for approval d. If approved, create the mandate, then proceed
How to Ask for Permission
When denied, present it clearly and concisely: I need to [ACTION] but don't have a mandate for it. ๐ [CATEGORY]: [what you want to do] ๐ฏ Target: [specific target] โฐ Suggested duration: [reasonable TTL] Want me to set this up? I can also create a broader mandate if you'd prefer (e.g., all emails to @company.com for 30 days). DO NOT: Bypass the check and do it anyway Ask repeatedly for the same thing if denied Create mandates yourself without user approval Pretend you checked when you didn't DO: Suggest templates when appropriate ("Want me to set up dev-tools?") Batch similar requests ("I'll need to run several git commands โ want a dev-tools mandate?") Log every action after completion Mention remaining limits when relevant ("3/20 daily emails used")
First-Time Setup
If check-action returns "hint": "templates", the ledger is empty. Guide the user: Agent Passport isn't set up yet. It takes 30 seconds: mandate-ledger.sh init agent:me "Your Name" "assistant" "openclaw" mandate-ledger.sh create-from-template dev-tools Want me to run this for you?
Logging Actions
After every authorized action, log it: $SCRIPT_DIR/mandate-ledger.sh log-action "<mandate_id>" <amount> "<description>" For financial: amount = dollars spent For everything else: amount = 1 Description should be human-readable: "Sent email to bob@company.com re: Q1 report"
Kill Switch Behavior
If the user engages the kill switch, all operations are frozen until unlocked. ./mandate-ledger.sh kill "user requested freeze" ./mandate-ledger.sh unlock Agent behavior when kill switch is active: Do not attempt sensitive actions Do not retry check-action in a loop Tell user operations are blocked and request explicit unlock
Overview
Agent Passport provides a consent layer for agent autonomy. Instead of all-or-nothing permissions, users grant mandates with specific constraints: "I authorize this agent to [ACTION] with [CONSTRAINTS] until [EXPIRY]" This isn't just about purchases โ it's consent-gating for all sensitive actions.
Action Categories
CategoryExamplesTypical ConstraintsfinancialPurchases, transfers, subscriptionsSpending cap, merchant allowlistcommunicationEmails, messages, tweets, postsRecipient allowlist, rate limitdataDelete files, edit docs, DB writesPath allowlist, require backupsystemShell commands, installs, configsCommand allowlist, no sudoexternal_apiThird-party API callsService allowlist, rate limitidentityPublic actions "as" the userHuman review required
Wildcard Patterns
Allowlists and deny lists support three wildcard styles: PatternMatchesExampleprefix *Anything starting with prefixgit * โ git pull, git status*.suffixAnything ending with suffix*.env โ config.env, .env*middle*Anything containing middle*/.git/* โ repo/.git/config*@domainEmail domain match*@company.com โ bob@company.comexactExact match onlyapi.github.com
Modes
Local mode (default): Mandates stored in ~/.openclaw/agent-passport/. Free tier is fully offline. Pro tier makes periodic API calls to api.agentpassportai.com for license validation and threat definition updates. Preview mode: No storage, no network. Generates validated payloads and curl templates. Live mode (roadmap): Future connection to Agent Bridge backend for multi-agent sync and compliance. Not yet implemented.
Quick Start Commands
# Initialize with identity ./mandate-ledger.sh init <agent_id> <principal> [scope] [provider] # Templates (auto-detects agent if registered) ./mandate-ledger.sh templates ./mandate-ledger.sh create-from-template dev-tools ./mandate-ledger.sh create-from-template email-team <domain> ./mandate-ledger.sh create-from-template file-ops <path> ./mandate-ledger.sh create-from-template web-research ./mandate-ledger.sh create-from-template safe-browsing ./mandate-ledger.sh create-from-template coding ./mandate-ledger.sh create-from-template email-assistant ./mandate-ledger.sh create-from-template read-only ./mandate-ledger.sh create-from-template full-auto # Quick create (human-friendly durations: 7d, 24h, 30m) ./mandate-ledger.sh create-quick <type> <agent_id> <allowlist_csv> <duration> [amount_cap] # Check & log ./mandate-ledger.sh check-action <agent> <type> <target> [amount] ./mandate-ledger.sh log-action <mandate_id> <amount> "<description>" # Audit ./mandate-ledger.sh audit [limit] ./mandate-ledger.sh summary # Threat definitions ./mandate-ledger.sh init-definitions ./mandate-ledger.sh update-definitions ./mandate-ledger.sh definitions-status
Quick Start
init [agent_id] [principal] [scope] [provider] # Initialize ledger, optionally register agent templates # List available templates create-from-template <t> # Create mandate from template [agent_id] [args...] create-quick <type> # Create with positional args <agent_id> <allowlist> <duration> [amount_cap]
Mandate Lifecycle
create <json> # Create mandate (include action_type) create-with-kya <json> # Create with auto-attached agent KYA get <mandate_id> # Get mandate by ID list [filter] # List mandates (all|active|revoked|<action_type>) revoke <mandate_id> [why] # Revoke a mandate
Authorization
check-action <agent> <type> <target> [amount] # Check if action is authorized log-action <mandate_id> <amount> [description] # Log action against mandate kill <reason> # Engage kill switch and freeze execution unlock # Disengage kill switch
Audit & Reporting
audit [limit] # Show recent audit entries audit-mandate <id> # Show audit for specific mandate audit-summary [since] # Summary by action type summary # Show overall ledger stats export # Export full ledger as JSON
Threat Definitions
init-definitions # Write bundled threat-definitions.json to LEDGER_DIR update-definitions # Refresh definitions (Pro: API pull, Free: bundled copy) [--force] [--offline] definitions-status # Show version, pattern counts, and last update
KYA (Know Your Agent)
kya-register <agent_id> <principal> <scope> [provider] kya-get <agent_id> kya-list kya-revoke <agent_id> [why]
Mandate Structure
{ "mandate_id": "mandate_1770412575_3039e369", "action_type": "communication", "agent_id": "agent:my-assistant", "scope": { "allowlist": ["*@mycompany.com", "bob@partner.com"], "deny": ["*@competitor.com"], "rate_limit": "20/day", "kya": { "status": "verified", "verified_principal": "Mark" } }, "amount_cap": null, "ttl": "2026-02-13T00:00:00Z", "status": "active", "usage": { "count": 5, "total_amount": 0 }, "created_at": "2026-02-06T22:00:00Z" }
Agent Bridge (Future Roadmap)
Note: Free tier is fully local with no network calls. Pro tier (AGENT_PASSPORT_LICENSE_KEY set) makes periodic HTTPS calls to api.agentpassportai.com for license validation and threat definition updates. No usage data or scan results are transmitted. Agent Bridge is a planned future service. Local mode handles single-user, single-agent scenarios. A future Agent Bridge service would add: Multi-agent coordination โ prevent overlapping mandates Cross-device sync โ same mandates everywhere Organization policies โ IT guardrails, user customization within Compliance reporting โ audit exports for regulatory needs Merchant/service registry โ verified vendors, trust scores Export local ledger anytime: ./mandate-ledger.sh export > backup.json
Configuration (OpenClaw)
{ "skills": { "entries": { "agent-passport": { "env": { "AGENT_PASSPORT_LOCAL_LEDGER": "true" }, "config": { "default_currency": "USD", "default_ttl_minutes": 60, "confirm_threshold_amount": 50 } } } } }
Storage
All data stored locally in ~/.openclaw/agent-passport/: mandates.json โ mandate ledger agents.json โ KYA registry audit.json โ action audit trail threat-definitions.json โ active threat pattern definitions threat-definitions.bak โ previous definitions backup .threat-meta.json โ last update/version/source metadata
Safety
Never leak secrets into prompts, logs, or outputs Mandates constrain actions, but don't prevent all misuse Audit trail provides accountability, not prevention Use KYA to verify agent identity before granting broad mandates
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
4 Docs2 Config
- SKILL.md
- README.md
- references/mandates.md
- TRADEMARK.md
- _meta.json
- agents/openai.yaml