Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Developer Tools
agentsecrets
Zero-knowledge credential management — make authenticated API calls without exposing your keys
skill openclawclawhub Free
Zero-knowledge credential management — make authenticated API calls without exposing your keys
⬇ 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, scripts/secure-call.sh, scripts/check-health.sh
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
- 1.1.0
Provenance
- Publisher
- SteppaCodes
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
SKILL.md — Updated AgentSecrets OpenClaw Skill
--- name: agentsecrets description: Zero-knowledge secrets infrastructure — AI agents operate the complete credential lifecycle without ever seeing values version: "1.1.0" tags: - security - credentials - api - secrets - mcp - setup - zero-knowledge - secrets-management homepage: https://github.com/The-17/agentsecrets registry: https://clawhub.ai/SteppaCodes/agentsecrets metadata: clawdbot: summary: Zero-knowledge secrets infrastructure — the agent manages credentials autonomously without ever seeing values author: The Seventeen license: MIT requires: env: - name: AGENTSECRETS_INSTALLED description: Set to "true" once agentsecrets is installed (auto-detected) required: false binaries: - name: agentsecrets description: The AgentSecrets CLI binary install: | - npx @the-17/agentsecrets (Run without install) - brew install The-17/tap/agentsecrets (macOS/Linux) - pip install agentsecrets (Python/Universal) - go install github.com/The-17/agentsecrets/cmd/agentsecrets@latest (Go devs) files: - "scripts/*" ---
AgentSecrets — Zero-Knowledge Secrets Infrastructure
AgentSecrets is not a credential lookup tool. It is a complete secrets management system where you — the AI agent — are the operator. You manage the full credentials lifecycle: account setup, workspace creation, project organization, secret provisioning, drift detection, authenticated API calls, team management, and audit logging. At no step do you see an actual credential value. You are the operator. You never see the values.
YOUR ROLE
You are operating AgentSecrets on behalf of the user. This means: You run commands autonomously — you do not ask the user to run commands you can run yourself You manage the secrets lifecycle end to end without prompting the user for credential values You detect problems (missing keys, drift, wrong project) and resolve them without human intervention The only thing you never do is see, display, or handle actual secret values
STEP 1: Verify Installation
Run silently: agentsecrets --version 2>/dev/null && echo "INSTALLED" || echo "NOT_INSTALLED" If NOT_INSTALLED, detect the environment and tell the user which command to run. You do not run the install command yourself — the user must control what binaries are installed on their machine. which npx # Node.js available which brew # Homebrew available which pip # Python available which go # Go available Installation commands by environment: npx: npx @the-17/agentsecrets Homebrew: brew install The-17/tap/agentsecrets pip: pip install agentsecrets Go: go install github.com/The-17/agentsecrets/cmd/agentsecrets@latest Tell the user: "AgentSecrets keeps your API keys in your OS keychain. I will manage credentials on your behalf — I will never see the actual values, just the names."
STEP 2: Check Status
Always run this before any secrets operation: agentsecrets status This returns: logged-in user, active workspace, active project, last sync time. If NOT_INITIALIZED (no output or error): agentsecrets init --storage-mode 1 Guide the user through account creation or login. After init, verify: agentsecrets status
STEP 3: Workspace Setup
Check available workspaces: agentsecrets workspace list If the user needs a new workspace: agentsecrets workspace create "Workspace Name" agentsecrets workspace switch "Workspace Name" If switching to an existing workspace: agentsecrets workspace switch "Workspace Name" Invite teammates when requested: agentsecrets workspace invite user@email.com
STEP 4: Project Setup
AgentSecrets organizes secrets by project. For OpenClaw workflows, use the dedicated OPENCLAW_MANAGER project. Check if it exists: agentsecrets project list 2>/dev/null | grep -q "OPENCLAW_MANAGER" && echo "EXISTS" || echo "NOT_FOUND" If EXISTS: agentsecrets project use OPENCLAW_MANAGER If NOT_FOUND: agentsecrets project create OPENCLAW_MANAGER agentsecrets project use OPENCLAW_MANAGER For non-OpenClaw workflows, use or create the appropriate project: agentsecrets project list agentsecrets project use PROJECT_NAME # or agentsecrets project create PROJECT_NAME agentsecrets project use PROJECT_NAME
STEP 5: Secret Provisioning
Before making any API call, verify the required secret exists: agentsecrets secrets list You will see key names only. Never values. If a required key is missing, never ask the user to paste the value into chat. Tell them: "I need KEY_NAME to complete this. Please run this in your terminal: agentsecrets secrets set KEY_NAME=value Let me know when done and I will proceed." Wait for confirmation, then verify: agentsecrets secrets list Standard key naming conventions: ServiceKey NameStripe (live)STRIPE_KEY or STRIPE_LIVE_KEYStripe (test)STRIPE_TEST_KEYOpenAIOPENAI_KEYGitHubGITHUB_TOKENGoogle MapsGOOGLE_MAPS_KEYAWSAWS_ACCESS_KEY and AWS_SECRET_KEYPaystackPAYSTACK_KEYSendGridSENDGRID_KEYTwilioTWILIO_SID and TWILIO_TOKENAny otherSERVICENAME_KEY (uppercase, underscores)
STEP 6: Detect and Resolve Drift
Before deployment workflows or when secrets may be stale: agentsecrets secrets diff This shows what is out of sync between local keychain and cloud. If drift is detected: agentsecrets secrets pull To push local changes to cloud: agentsecrets secrets push
STEP 7: Make Authenticated API Calls
Always use agentsecrets call — never curl or direct HTTP with credentials. Basic pattern: agentsecrets call --url <URL> --method <METHOD> --<AUTH_STYLE> <KEY_NAME> Default method is GET if --method is omitted. Auth styles: PatternFlagUse ForBearer token--bearer KEY_NAMEStripe, OpenAI, GitHub, most modern APIsCustom header--header Name=KEY_NAMESendGrid, Twilio, API GatewayQuery parameter--query param=KEY_NAMEGoogle Maps, weather APIsBasic auth--basic KEY_NAMEJira, legacy REST APIsJSON body--body-field path=KEY_NAMEOAuth flows, custom authForm field--form-field field=KEY_NAMEForm-based auth Examples: # GET request agentsecrets call --url https://api.stripe.com/v1/balance --bearer STRIPE_KEY # POST with body agentsecrets call \ --url https://api.stripe.com/v1/charges \ --method POST \ --bearer STRIPE_KEY \ --body '{"amount":1000,"currency":"usd","source":"tok_visa"}' # PUT request agentsecrets call \ --url https://api.example.com/resource/123 \ --method PUT \ --bearer API_KEY \ --body '{"field":"value"}' # DELETE request agentsecrets call \ --url https://api.example.com/resource/123 \ --method DELETE \ --bearer API_KEY # Custom header agentsecrets call \ --url https://api.sendgrid.com/v3/mail/send \ --method POST \ --header X-Api-Key=SENDGRID_KEY \ --body '{"personalizations":[...]}' # Query parameter agentsecrets call \ --url "https://maps.googleapis.com/maps/api/geocode/json?address=Lagos" \ --query key=GOOGLE_MAPS_KEY # Multiple credentials agentsecrets call \ --url https://api.example.com/data \ --bearer AUTH_TOKEN \ --header X-Org-ID=ORG_SECRET # Basic auth agentsecrets call \ --url https://jira.example.com/rest/api/2/issue \ --basic JIRA_CREDS # Paystack agentsecrets call \ --url https://api.paystack.co/transaction/initialize \ --method POST \ --bearer PAYSTACK_KEY \ --body '{"email":"user@example.com","amount":10000}'
STEP 8: Proxy Mode
For workflows requiring multiple calls or framework integrations: agentsecrets proxy start agentsecrets proxy status agentsecrets proxy stop With custom port: agentsecrets proxy start --port 9000 HTTP proxy pattern for any agent or framework: POST http://localhost:8765/proxy X-AS-Target-URL: https://api.stripe.com/v1/balance X-AS-Inject-Bearer: STRIPE_KEY
STEP 9: Audit What Happened
After any significant operation: agentsecrets proxy logs agentsecrets proxy logs --last 20 agentsecrets proxy logs --secret STRIPE_KEY Output shows: timestamp, method, target URL, key name, status code, duration, and redaction status. Never shows values. If you see (REDACTED) in the logs, it means AgentSecrets detected that an API echoed back the injected credential and automatically replaced it with [REDACTED_BY_AGENTSECRETS] before the response reached you. The audit reason will show credential_echo. This is expected security behavior. Raw log location: ~/.agentsecrets/proxy.log (JSONL format)
STEP 10: Environment Variable Injection
When a tool needs secrets as environment variables (Stripe CLI, Node.js, dev servers, SDKs), use agentsecrets env instead of agentsecrets call: agentsecrets env -- stripe mcp agentsecrets env -- node server.js agentsecrets env -- npm run dev This resolves all secrets from the active project's keychain and injects them as environment variables into the child process. Values exist only in the child process memory — nothing is written to disk. Use this when: The user wants to run a CLI tool that reads credentials from env vars You need to wrap a native MCP server (e.g., Stripe MCP) The user says "inject secrets into my app" or "run X with my API keys"
Account
agentsecrets init # Create account or login agentsecrets init --storage-mode 1 # Init with keychain-only mode agentsecrets login # Login to existing account agentsecrets logout # Clear session agentsecrets status # Current context
Workspaces
agentsecrets workspace create "Name" # Create workspace agentsecrets workspace list # List all workspaces agentsecrets workspace switch "Name" # Switch active workspace agentsecrets workspace invite user@email # Invite teammate
Projects
agentsecrets project create NAME # Create project agentsecrets project list # List projects in workspace agentsecrets project use NAME # Set active project agentsecrets project update NAME # Update project agentsecrets project delete NAME # Delete project
Secrets
agentsecrets secrets set KEY=value # Store secret agentsecrets secrets get KEY # Retrieve value (user sees it, you don't) agentsecrets secrets list # List key names only agentsecrets secrets list --project NAME # List keys for specific project agentsecrets secrets push # Upload .env to cloud (encrypted) agentsecrets secrets pull # Download cloud secrets to keychain agentsecrets secrets delete KEY # Remove secret agentsecrets secrets diff # Compare local vs cloud
Calls and Proxy
agentsecrets call --url URL --bearer KEY # One-shot authenticated call agentsecrets call --url URL --method POST --bearer KEY --body '{}' agentsecrets call --url URL --header Name=KEY agentsecrets call --url URL --query param=KEY agentsecrets call --url URL --basic KEY agentsecrets call --url URL --body-field path=KEY agentsecrets call --url URL --form-field field=KEY agentsecrets proxy start # Start HTTP proxy agentsecrets proxy start --port 9000 # Custom port agentsecrets proxy status # Check proxy status agentsecrets proxy stop # Stop proxy agentsecrets proxy logs # View audit log agentsecrets proxy logs --last N # Last N entries agentsecrets proxy logs --secret KEY # Filter by key name
MCP
agentsecrets mcp serve # Start MCP server agentsecrets mcp install # Auto-configure Claude Desktop + Cursor
Environment Injection
agentsecrets env -- <command> [args...] # Inject secrets as env vars into child process agentsecrets env -- stripe mcp # Wrap Stripe MCP agentsecrets env -- node server.js # Wrap Node.js agentsecrets env -- npm run dev # Wrap any dev server
Workspace Security
agentsecrets workspace allowlist add <domain> [domain...] # Authorize domains (multi-domain) agentsecrets workspace allowlist list # List allowed domains agentsecrets workspace allowlist log # View blocked attempts agentsecrets workspace promote user@email.com # Grant admin role agentsecrets workspace demote user@email.com # Revoke admin role
First time setup
Run Steps 1 through 5 in sequence. Do not skip steps.
"Make an API call to X"
agentsecrets status — verify context agentsecrets secrets list — check key exists agentsecrets call — make the call Return response to user
"Deploy to production"
agentsecrets workspace switch production agentsecrets secrets diff — check for drift agentsecrets secrets pull — sync if needed Run deployment agentsecrets proxy logs — audit
"Invite a teammate"
agentsecrets workspace invite teammate@company.com
"Rotate a key"
Tell user to run: agentsecrets secrets set KEY_NAME=new_value in their terminal Verify: agentsecrets secrets list Push to cloud: agentsecrets secrets push
"What keys do I have?"
agentsecrets secrets list
"Check audit log"
agentsecrets proxy logs --last 50
API Call Blocked by Zero-Trust Allowlist
If an API call returns a 403 error stating the domain is not in the workspace allowlist: Do not bypass the proxy. Tell the user exactly what to run in their terminal to authorize the domain: agentsecrets workspace allowlist add <domain> You can also suggest adding multiple domains at once: agentsecrets workspace allowlist add api.stripe.com api.openai.com (Wait for their confirmation that they have entered their password and added the domain) Retry the API call.
User Needs Secrets as Environment Variables
agentsecrets status — verify context agentsecrets secrets list — verify key exists agentsecrets env -- <command> — wrap the command
CRITICAL RULES
NEVER display, echo, print, or log an actual secret value NEVER ask the user to paste a key value into chat NEVER use curl or direct HTTP for authenticated requests — always use agentsecrets call ALWAYS run agentsecrets status before any secrets operation in a new session ALWAYS run agentsecrets secrets diff before deployment workflows ALWAYS suggest the user delete any chat message where they mentioned a raw key value You are the operator — manage the lifecycle autonomously, do not delegate commands back to the user unless it involves installing software, entering a password, or modifying the Zero-Trust Allowlist. Respect the Zero-Trust Allowlist — if a domain is blocked, instruct the user to run agentsecrets workspace allowlist add <domain>. When wrapping CLI tools that need env vars, use agentsecrets env -- <command> instead of exporting values manually. If you see (REDACTED) in proxy logs, explain that AgentSecrets detected and scrubbed a credential echo — this is expected security behavior.
Security Model
Zero-knowledge: credential values never enter your context at any step Zero-trust: deny-by-default domain allowlist blocks unauthorized outbound requests Response body redaction: if an API echoes back the injected credential, the proxy scrubs it with [REDACTED_BY_AGENTSECRETS] before it reaches you OS keychain: macOS Keychain, Windows Credential Manager, Linux Secret Service Server: stores encrypted blobs only — cannot decrypt Audit trail: key names only, no value field exists in the log struct Encryption: X25519 + AES-256-GCM + Argon2id Role management: only workspace admins can modify the allowlist (requires password)
Trust Statement
AgentSecrets is open source (MIT). Full source at https://github.com/The-17/agentsecrets. All credential resolution is local — nothing leaves the user's machine except the outbound API request itself.
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Docs2 Scripts
- SKILL.md
- README.md
- scripts/check-health.sh
- scripts/secure-call.sh