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/dmzoneill/redhat-ai-workflow/setup-gmailgit clone --depth 1 https://github.com/dmzoneill/redhat-ai-workflowWhat 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.00845 |
| Opus 5 | $0.00000 | $0.00423 |
| Sonnet 5 | $0.00000 | $0.00169 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
setup-gmail 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup-gmail
Enable Gmail access for the /coffee command and email features.
Overview
Enable Gmail access for the /coffee command and email features.
Underlying Skill: coffee
This command is a wrapper that calls the coffee skill. For detailed process information, see skills/coffee.md.
Arguments
No arguments required.
Usage
Examples
## Setup Steps
Gmail uses the same Google OAuth as Calendar, but needs additional scopes.
### Step 1: Enable Gmail API in Google Cloud
1. Go to [Google Cloud Console](https://console.cloud.google.com)
2. Select your project (same one used for Calendar)
3. Navigate to **APIs & Services** → **Library**
4. Search for **Gmail API**
5. Click **Enable**
### Step 2: Update OAuth Scopes
Your existing OAuth app needs to request Gmail permissions:
1. Go to **APIs & Services** → **OAuth consent screen**
2. Click **Edit App**
3. In **Scopes**, add:
- `https://www.googleapis.com/auth/gmail.readonly`
- `https://www.googleapis.com/auth/gmail.modify`
4. Save
### Step 3: Re-authenticate
Delete the existing token and re-authenticate to get Gmail access:
Then run:
Sign in and grant the new Gmail permissions.
### Step 4: Verify
Test email access:
Process Flow
This command invokes the coffee skill. The process flow is:
flowchart LR
START([User runs /setup-gmail]) --> VALIDATE[Validate Arguments]
VALIDATE --> CALL[Call coffee skill]
CALL --> EXECUTE[Execute Skill Steps]
EXECUTE --> RESULT[Return Result]
RESULT --> END([Complete])
style START fill:#6366f1,stroke:#4f46e5,color:#fff
style END fill:#10b981,stroke:#059669,color:#fff
style CALL fill:#3b82f6,stroke:#2563eb,color:#fff
For detailed step-by-step process, see the coffee skill documentation.
Details
Current Status
First, check if Gmail is already working:
google_calendar_status()
Setup Steps
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.
- 2d ago First seen · 156 lines · 0 tokens per session scan A 1ed1cbb8056c
setup-gmail is a command published in the GitHub repository dmzoneill/redhat-ai-workflow (5 stars, last pushed 23d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 845 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
pr-address
Address PR review comments on current branch.
validate_changed_docstrings
Validates Python docstrings in all uncommitted changed files using Sphinx parsing.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
triage
Triage Linear issue with comprehensive analysis.
mass-line
用群众路线收集多源信息、整合反馈并返回验证。.