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 skills/openclaw/gogcli/gog-tasksnpx skills add openclaw/gogcli --skill gog-tasksgit clone --depth 1 https://github.com/openclaw/gogcliWhat 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.00011 | $0.00353 |
| Opus 5 | $0.00005 | $0.00177 |
| Sonnet 5 | $0.00002 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
gog-tasks 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 today.
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
Google Tasks
Use gog for Google Tasks operations. Read ../gog/SKILL.md first for shared auth,
output, safety, and live-write rules.
Safe start
gog auth list --check --json --no-input
gog schema tasks --json
gog --readonly --account [email protected] tasks lists list --json --wrap-untrusted
- Select the account explicitly with
--account. - Use
--json --wrap-untrustedfor agent-readable Google content. - Use
--readonlywhen the task must not mutate Google data. - Use
--no-inputin automation and--dry-runbefore supported writes. - Confirm the exact account, object, and mutation before any write or delete.
Commands
| Command | Purpose |
|---|---|
add |
Add a task |
clear |
Clear completed tasks |
delete |
Delete a task |
done |
Mark task completed |
get |
Get a task |
list |
List tasks |
lists |
List task lists |
raw |
Dump raw Google Tasks API response as JSON (Tasks.Get; lossless; for scripting and LLM consumption) |
undo |
Mark task needs action |
update |
Update a task |
Run gog tasks <command> --help for flags and gog schema tasks <command> --json
for the machine-readable contract. Do not guess command syntax.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 44 lines · 11 tokens per session scan A f7e40d8cf457
gog-tasks is a skill published in the GitHub repository openclaw/gogcli (8,363 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 353 once invoked, about $0.0001 per session on Opus 5. 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-09-03.
Other skills, from other repositories
gmail
Send, read, and manage Gmail messages and email attachments automatically.
cloud-build-basics
Teaches the fundamentals of Google Cloud Build (GCB). Covers core concepts, API enablement, console navigation to the Build History page, and the end-to-end workflow for creating and manually running a basic build trigger. Do not use for managing private pools or complex pipeline architectures.
detection-engineering-coverage-evaluation
Automates the end-to-end detection engineering workflow in Google SecOps using MCP tools. Use when fetching threat intelligence from blogs, generating Threat Detection Opportunities (TDOs), simulating attacker behavior with synthetic UDM events, evaluating rule coverage, generating new YARA-L 2.0 rules to close…
managing-google-workspace
Manages Google Workspace operations across 12 services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts, Chat, Apps Script, Custom Search). Supports MCP tools or CLI via uvx workspace-mcp --cli. Provides tool routing, workflows, and parameter guidance for 114 tools. Triggers for "check my email"…
google-tasks-tool
Google Tasks integration for listing task lists and tasks and creating or updating tasks via OAuth2. Use when: fetching TODO lists, adding tasks, marking items complete, or switching task lists.
google-calendar-tool
Google Calendar integration tool for listing and creating events via OAuth2 Calendar API access. Use when: checking upcoming events, creating appointments, or updating your schedule.