I use pass for exporting secrets to environment variables. I have a multi-line password called "envvars" that contains a script like this: #!/usr/bin/fish

I use pass for exporting secrets to environment variables. I have a multi-line password called "envvars" that contains a script like this: #!/usr/bin/fish set -x PASSWORD hunter2 set -x PASSWORD_STG hunter3 set -x LUGGAGE_KEY 12345 set -x TOKEN (curl "https://api.example.com/oauth/token" \ --data-urlencode "username=$USERNAME" \ --data-urlencode "password=$PASSWORD" | jq --raw-output .access_token) set -x TOKEN_STG (curl "https://api-stg.example.com/oauth/token" \ --data-urlencode "username=$USERNAME_STG" \ --data-urlencode "password=$PASSWORD_STG" | jq --raw-output .access_token) When I want to set the environment variables I run `pass show envvars | source` and it sets the environment variables for the current shell. It's an easy way to keep the secrets out of my shell history and plaintext files.