authy
by eric8810
AI & LLMsBrief
Inject secrets into subprocesses via environment variables.
Description
What This Skill Does
Authy injects secrets into subprocesses as environment variables without ever exposing their values. The `authy run` command passes credentials directly to child processes, keeping them out of shell history, logs, and script files. Secret names are discoverable via `authy list`; values are never returned to the caller.
Unlike exporting env vars manually or using .env files, secrets never appear in shell history, process listings, or on disk at any point.
When to Use It
- Running a deploy script with production API keys
- Starting a backend server with database credentials
- Executing tests that require third-party service tokens
- Injecting cloud provider credentials into a CI build step
- Running a curl request with a bearer token from a secret store
Example Workflow
User asks: Run my deploy script using secrets from the 'deploy' scope
- 1
Run
authy list --scope deploy --jsonto discover available secret names - 2
Identify the secret names needed by the deploy script
- 3
Construct the authy run command with --scope deploy --uppercase --replace-dash '_'
- 4
Execute:
authy run --scope deploy --uppercase --replace-dash '_' -- ./deploy.sh - 5
Confirm exit code 0 indicating successful secret injection and script execution
deploy.sh runs with secrets like DB_HOST and API_KEY injected as environment variables, values never visible in the shell or logs
Requirements
- authy binary installed and available on PATH
- AUTHY_TOKEN environment variable
- AUTHY_KEYFILE environment variable (path to local key file)
Installation
clawhub install eric8810/authyRun the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.