credential-brokers
User-scope credential brokering so credentialed skills never touch a repo’s
files for secrets. This is the pack the other credentialed packs (atlassian,
figma) depend on.
What’s inside
Section titled “What’s inside”credbroker— a pip-installable Python library thatauth: credsskills resolve credentials through, imported in-process (env var → OS keychain →0600dotfile floor).sso-broker— a subprocess at~/.agentbundle/bin/forauth: sso-cookieskills. Its companion loader,credentials_shim, still ships as internal plumbing for this rail.credential-setup— one LLM-cooperative skill that walks a user through storing credentials.
Install
Section titled “Install”credential-brokers is user-scope by default — credentials belong to the
user, not the project. The broker is written to ~/.agentbundle/bin/ behind
the .agentbundle/ user-prefix fence.
agentbundle install --pack credential-brokers --scope user <catalogue>Set up credentials
Section titled “Set up credentials”After installing a credentialed pack, tell your agent “set up credentials”.
That triggers the interactive credential-setup skill, which prompts you for
each key the skill needs and stores it at the highest-available tier — your OS
keychain on macOS/Windows, or a 0600 dotfile (~/.agentbundle/credentials.env)
on Linux.
You: set up credentialsAgent: (runs credential-setup; prompts you for each token interactively)Two rules the broker enforces, by design: secrets never go on the command
line (the setup script refuses --token / --pat / --password flags), and
the agent never runs the setup for you — it’s interactive and user-invoked,
so the token is entered by you and never echoed back into the transcript.
You don’t invoke the broker directly — credentialed skills (e.g. jira,
figma) resolve their token through it automatically once credential-setup
has stored it. Re-run “set up credentials” any time you need to add or
rotate a key.
→ Go deeper: the credential-brokers guides.