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/ehmo/gum/gum-logingit clone --depth 1 https://github.com/ehmo/gumWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/ehmo/gum/gum-login)<a href="https://agentmods.dev/commands/ehmo/gum/gum-login"><img src="https://agentmods.dev/badge/commands/ehmo/gum/gum-login.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00000 | $0.00325 |
| Opus 5 | $0.00000 | $0.00162 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
gum-login 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 6d ago.
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.
What it actually says
gum login
Generated from
gum schema --json. Do not edit this page by hand; runmake docs-commands.
Authorize gum (alias for gum auth login)
Usage
gum login [flags]
Parent
Flags
| Flag | Type | Default | Help |
|---|---|---|---|
--all |
bool |
false | Request the full catalog scope union (every service). Default is the core Workspace set; the full union needs all those APIs enabled on your OAuth client. |
--no-browser |
bool |
false | Print the URL but don't launch a browser (use for SSH/devcontainer/headless) |
--scope |
stringSlice |
[] | Exact OAuth scope(s) to request; repeat or comma-separate. Overrides --service/--all. |
--service |
stringSlice |
[] | Request only these services' scopes (e.g. --service people,youtube). Comma-separate or repeat. |
--log-format |
string |
json | Log format: json|text |
--log-level |
string |
info | Log level: debug|info|warn|error (overrides GUM_LOG_LEVEL) |
--profile |
string |
default | Profile name to read/write config under |
See also
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.
- 6d ago First seen · 33 lines · 0 tokens per session scan A 09781c1644db
gum-login is a command published in the GitHub repository ehmo/gum (32 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 325 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-30.
Other commands, from other repositories
/openspec-apply
Implement an approved OpenSpec change and keep tasks in sync.
/openspec-archive
Archive a deployed OpenSpec change and update specs.
/openspec-proposal
Scaffold a new OpenSpec change and validate strictly.
archive
name: OpenSpec: Archive description: Archive a deployed OpenSpec change and update specs. category: OpenSpec tags: [openspec, archive].
proposal
name: OpenSpec: Proposal description: Scaffold a new OpenSpec change and validate strictly. category: OpenSpec tags: [openspec, change].
apply
name: OpenSpec: Apply description: Implement an approved OpenSpec change and keep tasks in sync. category: OpenSpec tags: [openspec, apply].