secrets
v0.1.4Local protected secret store. Provider keys and other credentials are encrypted under a master key kept outside the project (secret://NAME) or kept as variables in the project's .env (env://NAME), referenced from versioned configuration and resolved only by the workers each secret allowlists; metadata reads never return a value, and the secrets::changed trigger reports rotations and .env edits.
Install
bash
iii trigger compose::add worker=secrets@nextRun in your project with the iii engine running. Exact versions are immutable and digest-pinned.
No skills or prompts attached
This worker version has no skills or prompts published yet.