Skip to content
Back to skills

Cli Auth

ASecurity

Obtain CLI access tokens via the daimon MCP server's get_cli_token tool.

  • 17 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 5, 2026
ai-agentsgoshellgit

Works with

  • cli
  • mcp

Security analysis

A100/100

Scanned September 21, 2026

npx -y skills add pymc-labs/daimon --skill cli-auth --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cli Auth?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cli Auth
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pymc-labs-cli-auth/badge)](https://www.skillsdirectory.com/skills/pymc-labs-cli-auth)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: cli-auth
description: Obtain 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 obtain access
tokens for external CLIs. Export the result under the appropriate name
before running CLI commands.

| Service                  | Tool call                  | Name to export                |
|--------------------------|----------------------------|-------------------------------|
| GitHub                   | `get_cli_token("github")`  | `GH_TOKEN` (or `GITHUB_TOKEN`)|
| Google Cloud / Workspace | `get_cli_token("gcloud")`  | `CLOUDSDK_AUTH_ACCESS_TOKEN`  |

Call the MCP tool first, then pass its result privately to the shell process
environment before running a command such as `gh repo list`.
`get_cli_token` is an MCP tool, not a shell command.

The tool requires:

- For `github`: the caller must already have a matching GitHub token binding.
  An account-only call reads the account's token; an agent-bound call reads
  that agent's token. Ordinary chat currently uses account-only identity, so
  `request_repo_binding` saving a target agent's token does not make it
  available to this tool. A GitHub App installation alone does not supply it
  either. If access is missing, ask the operator to configure CLI token access
  for the calling identity; do not repeatedly ask the person to bind the repo.
- For `gcloud`: the operator must configure deployment Google access and bind
  the agent to a Google identity with `daimon agents bind-google <agent>
  <email> --scopes <scope>`, repeating `--scopes` for additional scopes.
  Tokens are short-lived (≈1 hour) impersonated access tokens.
  The call also needs an agent-bound identity, which ordinary chat does not
  currently provide. Binding the Google identity alone cannot fix a missing
  caller `agent_id`; hand that limitation to the operator.

Each call resolves access afresh. GitHub returns the stored personal token;
Google mints a short-lived impersonated token. Never print either value.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.