Mint short-lived CLI access tokens via the daimon MCP server's get_cli_token tool.
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add pymc-labs/daimon --skill cli-auth --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cli Auth?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/pymc-labs-cli-auth)More formats (shields.io, HTML) on the badges page.
---
name: cli-auth
description: Mint short-lived CLI access tokens via the daimon MCP server's get_cli_token tool.
---
# cli-auth
Use the daimon MCP server's `get_cli_token(service)` tool to mint short-lived
access tokens for external CLIs. Export the result as the appropriate env var
before running CLI commands.
| Service | Tool call | Env var to export |
|--------------------------|----------------------------|-------------------------------|
| GitHub | `get_cli_token("github")` | `GH_TOKEN` (or `GITHUB_TOKEN`)|
| Google Cloud / Workspace | `get_cli_token("gcloud")` | `CLOUDSDK_AUTH_ACCESS_TOKEN` |
Example shell flow:
```bash
export GH_TOKEN=$(get_cli_token github)
gh repo list
```
The tool requires:
- For `github`: an operator (or a Discord user via `/agent-setup`) must have
bound a GitHub PAT. Tokens are minted from the persisted PAT.
- For `gcloud`: The agent must be bound to a Google identity
(`agent_google_binding`) with appropriate scopes, configured by an operator.
Tokens are short-lived (≈1 hour) impersonated access tokens.
Tokens are minted fresh per call and never cached.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
