agent-wormhole
Use Agent Wormhole for one-time sealed handoffs between autonomous agents, including encrypted mission briefs, scoped secrets, temporary artifacts, receipts, config drops, CLI/API usage, ECHO holder access, and Bankr x402 paid opens.
What this skill does
# Agent Wormhole Agent Wormhole opens a temporary encrypted passage for agent handoffs. The payload can be claimed once, then the channel collapses. ## Before First Use This skill executes the `@builtbyecho/agent-wormhole` npm package. Before running any `agent-wormhole` or `npx @builtbyecho/agent-wormhole` command for the first time in a session, tell the user: > About to install/run `@builtbyecho/agent-wormhole` (v0.1.2) from npm. It is an encrypted one-time-handoff CLI that writes payloads to a local `.agent-wormholes/` directory and (for holder/paid opens) calls `storage.builtbyecho.xyz` and the Bankr x402 endpoint. It does NOT sign transactions or access private keys. > > Proceed? (y/n) Wait for explicit confirmation before the first invocation. Subsequent calls in the same session do not need to re-prompt. Pin the version when invoking via `npx`: ```bash npx -p @builtbyecho/[email protected] agent-wormhole <args> ``` ## Links - Website: `https://www.builtbyecho.xyz` - Product page: `https://www.builtbyecho.xyz/agent-wormhole.html` - Source: `https://github.com/BuiltByEcho/agent-wormhole` - Package: `https://www.npmjs.com/package/@builtbyecho/agent-wormhole` - Hosted skill file: `https://www.builtbyecho.xyz/skills/agent-wormhole/SKILL.md` Use this skill when a task involves: - sending or receiving one-time agent handoffs - passing mission briefs, configs, receipts, files, or scoped secrets - using the `agent-wormhole` CLI or HTTP API - checking ECHO holder sponsored access - checking Bankr x402 paid open status - deploying or operating the VPS service ## Quick Commands From a project that has the package installed: ```bash agent-wormhole send --text "mission brief" --ttl 10m agent-wormhole send --file ./artifact.tgz --note "handoff bundle" agent-wormhole inspect <code> agent-wormhole receive <code> --out ./received agent-wormhole cleanup --delete-claimed-older-than 15m ``` For one-off use without installing globally: ```bash npx -p @builtbyecho/[email protected] agent-wormhole send --text "mission brief" ``` ## Mental Model - Codes are `id.secret`. - `id` locates stored metadata. - `secret` derives the AES-256-GCM decrypt key and is not stored. - Default TTL is 10 minutes. - Max TTL is 24 hours unless explicitly configured lower. - Default max payload is 5 MB. - Receipts are written for opens and claims. ## Access Paths - Local CLI/library opens record `access.path = local`. - Direct API holder opens require an EIP-191 signature from a wallet holding at least `50,000,000 ECHO` on Base and record `access.path = echo_holder`. - Bankr x402 paid opens are handled by `agent-wormhole-open` and record `access.path = x402_paid`. - Claiming is free. ## Live Endpoints - Direct holder/API route: `https://storage.builtbyecho.xyz/agent-wormhole` - Bankr x402 paid open: `https://x402.bankr.bot/0x2a16625fad3b0d840ac02c7c59edea3781e340ae/agent-wormhole-open` - Self-hosted local service default: `http://127.0.0.1:8791` ## Verification From the package root: ```bash npm test node --check src/cli.js node --check src/index.js node --check src/server.js npm pack --json --dry-run ``` For live health: ```bash curl -sS https://storage.builtbyecho.xyz/agent-wormhole/health ``` For Bankr status, check both registry and execution: ```bash bankr --config "$BANKR_OWNER_CONFIG" x402 list bankr x402 schema https://x402.bankr.bot/0x2a16625fad3b0d840ac02c7c59edea3781e340ae/agent-wormhole-open bankr --config "$BANKR_PAYER_CONFIG" x402 call -X POST -d '{"payload":"dGVzdA=="}' --max-payment 0.01 -y --raw https://x402.bankr.bot/0x2a16625fad3b0d840ac02c7c59edea3781e340ae/agent-wormhole-open ``` Set `BANKR_OWNER_CONFIG` to the endpoint owner/operator config and `BANKR_PAYER_CONFIG` to a separate payer config. Do not treat registry active status alone as proof that paid x402 execution works. A real paid call from a non-owner wallet is the proof. ## Safety - Do not paste wormhole codes into public channels unless the user explicitly wants the payload claimable by anyone there. - Do not log plaintext secrets or payloads. - Prefer short TTLs for secrets. - Use local cleanup commands for received artifacts when they are no longer needed. - Do not test Bankr paid endpoints with the same wallet that owns/deployed the endpoint.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".