← ClaudeAtlas

revenantworks-warden-keywardenlisted

Finds where every credential on the machine lives, without showing a value. Trigger to list where keys, tokens and passwords are stored (Credential Manager, gh, .env, settings, .mcp.json, Docker); to cut a gh token to least privilege or switch gh accounts; to rotate a key and update its users; after a key was printed, pasted or committed; to check a command that uses a token before it runs, even when told to just run it (a curl with an Authorization header, a token test); or say /rw-keywarden (inventory, scope, rotate, leak, preflight, refresh). Drives op or bw when present. Leak scans and commit email are shieldwarden's; rules and hooks gatewarden's; routine credentials agentwright's; vetting a vault MCP trustwarden's.
revenantworks/claude-skills · ★ 2 · AI & Automation · score 81
Install: claude install-skill revenantworks/claude-skills
# revenantworks-warden-keywarden *history in CHANGELOG.md · sources and parity register in SOURCES.md · Apache-2.0 (LICENSE)* Owns the **lifecycle of a credential**: where it lives, what it may do, who uses it, how it is replaced, and what to do when it escaped. Vaults, scanners and redaction hooks already exist; keywarden drives them and adds three things none of them gives: - **A failure-path pre-flight.** Before a command touches a credential, keywarden states what it prints on success, on an auth failure and on a crash, and refuses a shape that echoes the value. A verify command that fails can print the very key it was verifying (a 401 body, a traceback that reprs the request, `curl -v`). Claude's reflex fires on output already produced, not on a command about to run, so the check comes first. - **A fingerprint-only inventory** of every store on a Windows dev machine, the plaintext ones first: `env` blocks in Claude Code settings, `.mcp.json` server env and headers, `.env` files, a `store`-helper `~/.git-credentials`, a gh `hosts.yml` with a token in it. - **A consumer map.** Rows that share a fingerprint are linked, so a rotation has a checklist of every place the old value must leave. **Workflow:** Pre-flight → Inventory → (Scope | Rotate | Leak) → Verify → Report ## Safety rules — hold these before running anything - **Never print, log, write or commit a value.** Every script emits only `{kind, prefix_class, length, fingerprint}`; a crash reports