Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/roboco-io/ghx-cli/authgit clone --depth 1 https://github.com/roboco-io/ghx-cliWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00877 |
| Opus 5 | $0.00000 | $0.00439 |
| Sonnet 5 | $0.00000 | $0.00175 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
auth scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ghx auth
Manage GitHub authentication.
Synopsis
ghx auth <command> [flags]
Description
The auth command group provides authentication management for ghx-cli. It integrates with GitHub CLI for seamless authentication with fallback to environment variables.
Commands
| Command | Description |
|---|---|
status |
Show authentication status |
ghx auth status
Display current authentication status.
ghx auth status [flags]
Flags
| Flag | Description | Default |
|---|---|---|
--format |
Output format (table, json) | table |
Examples
# Check status
ghx auth status
# JSON output
ghx auth status --format json
Output
The status command displays:
- GitHub CLI Status: Whether
ghis installed - Environment Token: Whether
GITHUB_TOKENorGHX_TOKENis set - Token Availability: Whether a valid token is available
- Token Validity: Whether the token is valid and not expired
- Available Scopes: Token permission scopes
- Required Scopes: Scopes needed for ghx-cli features
Example Output
GitHub CLI Authentication Status
================================
Status: Ready
Details:
--------
GitHub CLI: Installed
Environment Token: Not set
Token: Available
Token Validity: Valid
Required Scopes: Available
Available Scopes: [admin:org delete_repo gist project repo workflow]
Required Scopes: [repo project]
Recommendation:
---------------
Authentication is properly configured
Authentication Methods
Method 1: GitHub CLI (Recommended)
ghx-cli automatically uses your GitHub CLI authentication:
# Login with GitHub CLI
gh auth login
# Verify
ghx auth status
Method 2: Environment Variables
Set a GitHub Personal Access Token:
# Using GITHUB_TOKEN
export GITHUB_TOKEN="ghp_your_token_here"
# Or using GHX_TOKEN
export GHX_TOKEN="ghp_your_token_here"
Method 3: Config File
Add token to config file (~/.ghx.yaml):
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 185 lines · 0 tokens per session scan A ebb153bb9625
auth is a command published in the GitHub repository roboco-io/ghx-cli (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 877 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.