@barneywohl/agentmint
v0.0.3
Published
Provision agent accounts (secrets, email, chat) and export configs for agent runtimes.
Maintainers
Readme
AgentMint
Provision agent accounts (secrets, chat, email) and export runtime configs for agent swarms.
Published package:
- npm:
@barneywohl/agentmint
Install
Global install (recommended):
npm i -g @barneywohl/agentmint
agentmint --helpQuick start (no providers)
This validates the CLI end-to-end without touching Bitwarden/Telegram/Slack.
# Create a new project manifest
mkdir -p /tmp/agentmint-demo
agentmint init -p /tmp/agentmint-demo
# Show what’s enabled/missing
agentmint doctor -p /tmp/agentmint-demo
# Export an example runtime config (OpenClaw)
agentmint export openclaw -p /tmp/agentmint-demo -o /tmp/agentmint-demo/out
ls -la /tmp/agentmint-demo/outProviders (Bitwarden / 1Password / Telegram / Slack)
Providers are disabled by default. Enable them in your project manifest:
/tmp/agentmint-demo/agentmint.yaml
providers:
bitwarden:
enabled: true
telegram:
enabled: true
slack:
enabled: true
# 1password:
# enabled: trueThen provision (example: Bitwarden):
# one-time Bitwarden unlock in your shell
bw login
export BW_SESSION="$(bw unlock --raw)"
agentmint provision -p /tmp/agentmint-demoCommands
agentmint init— create a project manifest (agentmint.yaml)agentmint doctor— validate provider configuration and show missing stepsagentmint provision— create provider resources (e.g., vault items)agentmint export <target>— export runtime config files (e.g.,openclaw)agentmint up <target>— provision + export in one go
Status
Early MVP scaffold. Intended workflow is:
agentmint init
agentmint doctor
agentmint provision
agentmint export openclawSecurity
- No secrets printed to stdout by default.
- Provider tokens/credentials should live in a vault (Bitwarden/1Password), not in plaintext on disk.
