Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Secrets management for AI agents. Never expose your API keys again.
Secrets management for AI agents. Never expose your API keys again.
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. 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.
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.
Secrets management for AI agents. Store API keys encrypted, make requests through Janee, never touch the real key.
Most skills tell you to store API keys in plaintext config files. One prompt injection, one leaked log, one compromised session β and your keys are exposed. Janee fixes this: Keys encrypted at rest β not plaintext JSON Agent never sees the real key β requests go through Janee Path-based policies β restrict what endpoints can be called Full audit trail β every request logged Kill switch β revoke access without rotating keys
npm install -g @true-and-useful/janee janee init
janee add Follow the prompts to add your API credentials. Keys are encrypted automatically.
Instead of calling APIs directly with your key, call them through Janee: # Old way (dangerous): curl -H "Authorization: Bearer sk_live_xxx" https://api.stripe.com/v1/balance # Janee way (safe): # Agent calls execute(capability, method, path) via MCP # Janee injects the key, agent never sees it
Install the OpenClaw plugin for native tool support: openclaw plugins install @true-and-useful/janee-openclaw Your agent now has: janee_list_services β see available APIs janee_execute β make requests through Janee janee_reload_config β hot-reload after config changes
Instead of storing your Moltbook key in ~/.config/moltbook/credentials.json: janee add moltbook -u https://www.moltbook.com/api/v1 -k YOUR_KEY Then use Janee to post: # Your agent calls: janee_execute(service="moltbook", method="POST", path="/posts", body=...) Your Moltbook key stays encrypted. Even if your agent is compromised, the key can't be exfiltrated.
services: stripe: baseUrl: https://api.stripe.com auth: type: bearer key: sk_live_xxx # encrypted moltbook: baseUrl: https://www.moltbook.com/api/v1 auth: type: bearer key: moltbook_sk_xxx # encrypted capabilities: stripe_readonly: service: stripe rules: allow: [GET *] deny: [POST *, DELETE *] moltbook: service: moltbook ttl: 1h autoApprove: true
βββββββββββββββ ββββββββββββ βββββββββββ β AI Agent βββββββΆβ Janee βββββββΆβ API β β β MCP β β HTTP β β βββββββββββββββ ββββββββββββ βββββββββββ β β No key Injects key + logs request
GitHub: https://github.com/rsdouglas/janee npm: https://www.npmjs.com/package/@true-and-useful/janee OpenClaw Plugin: https://www.npmjs.com/package/@true-and-useful/janee-openclaw
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.