<p align="center" <img src="assets/banner.png" alt="Skarbiec — one field, one use, no standing secret" width="100%" </p
Skarbiec: Secrets and Authentication Management for the AI Agent Era
Credential and Authentication Management for the AI Era.
Your devices hold your SSH keys, 2FA, API keys and card details. You don’t want your AI to send them to an external provider, right? Skarbiec holds your information in one accessible place — and makes sure only authorised AI have access to it.
Since it is in one place, it also becomes easy to go full yolo — and give your agent access to every secret you have so that it has nothing stopping it. But this is not all! With embedded browser use integration through Weles, every secret can be rotated and, if you are missing something, the agent can get a secret independently and save it for future use. Think of this as 1Password and Bitwarden reimagined for the AI Agent Era.
All Your Auth Needs Sorted with One Install of Skarbiec.
Install · Quick start · CLI · Examples · Security · Contributing
Skarbiec is an early public 0.2.x product, not a hosted secret manager or a claim that local brokering makes a compromised host safe. The complete local broker works without a Wisent account, network licence check, item limit, or paid seat. Operated fleet synchronization, retained organization audit, governance, and custodied recovery are separate planned services.
flowchart LR
W[Workload identity] -->|signed, nonced request| B[Local Skarbiec broker]
B -->|policy + exact field check| C[One-use capability]
C -->|one field, once| W
B --> A[Tamper-evident audit]Problem and intended users
Long-lived environment variables and copied credential files give every process that can read them the whole secret for an indefinite period. AI workloads make that boundary harder to review: operators need to know which identity requested which field, reject replay, revoke access, rotate recipients, and recover the vault without putting plaintext into prompts or audit logs.
Skarbiec serves:
- individual operators storing and using credentials on machines they
control;
- agent and service owners replacing standing read tokens with signed,
one-use acquisition;
- security and platform teams defining exact consumer, item, and field
grants and reviewing a hash-chained local journal;