DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to choose the correct credential value without exposing it with Session Knowledge

List variable names, then review ranked candidate values in masked form.

Credentials. Plaintext values are stored in vault.db at mode 0600 and creds get returns them, so keep output in masked form and never commit or sync the index directory.

Who it is forA developer who needs the staging or production DATABASE_URL or another key and remembers using several different values.

The problemThe same variable name often has several real values across apps and environments, and picking the wrong one causes errors.

The outcomeThe correct variable name and a ranked set of masked candidates, with the call site each one came from.

What you need first

  • Claude Code with session transcripts in ~/.claude/projects/
  • Python 3.10+ with FTS5 in the bundled sqlite3 (on macOS, install from python.org or run brew install python)
  • git and bash to clone and run install.sh
  • Terminal access to run the CLI and restart Claude Code

Steps

  1. git clone https://github.com/nameforjt-afk/session-knowledge.git
  2. cd session-knowledge then bash install.sh
  3. python3 -m sessionmcp.cli creds list
  4. python3 -m sessionmcp.cli creds get DATABASE_URL --masked (inferred, check the README)
  5. python3 -m sessionmcp.cli verify-redaction

Prompt for your agent

In the session-knowledge repo, call list_credentials to find the variable name for <service>, then call get_credential in masked form only. Expect ranked candidates with their call sites and no plaintext shown. Verify that the chosen candidate is not a documentation example before using it.

Caveat. Doc examples and made-up values are also extracted as candidates, so blacklist fakes with creds forget --fingerprint rather than deleting them, since deleting alone is undone by the next daily re-scan.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page