pawsby
Catalog

The secrets preset

Org guardrails for secrets: staged changes scanned before every commit, .env and secrets/ kept out of git, and Vault values never echoed, written from stdin, rotated after exposure.

Install

unbound-paws add secrets

Adds 2 skills, loaded before 4 actions. Run it in a project that has unbound-paws init.

What it adds

Before one of these actions, paws has Claude read the skill first.

  • vault

    Skill

    Mandatory guardrails for every HashiCorp Vault operation (kv get, put, patch, delete, token create, policy write, lease revoke) via the vault CLI. Enforces the secrets-management baseline with Vault mechanics: -field piped retrieval, stdin writes, patch-and-burn rotation, narrow-policy short-TTL tokens, dynamic creds, and stated-purpose prod reads. Triggers PROACTIVELY on any `vault kv`, `vault token`, or `vault lease` invocation — do NOT wait for the user to invoke it.

    Runs before

    • Secrets are read, written or deleted, tokens created

      vault kv get …

    • A Vault MCP secret write, delete or token create

      Vault MCP · write_secret, delete_secret …

  • secret-scan

    Skill

    Check staged changes for secrets before every git commit, and keep .env and secrets/ files out of git. Use before any commit and before writing or editing a .env file or anything under secrets/.

    Runs before

    • A commit

      git commit

    • A .env file or anything under secrets/ is written

      edit {.env,.env.*,**/secrets/**}