gtasks-todo-manager

A task manager for Google Tasks that works across multiple Google accounts, including personal Gmail and work accounts.

In plain words
What is it for?
Create, edit, complete, organize, and review tasks and task lists across Google accounts.
Why use it?
It keeps tasks from different accounts in one place, so you do not need to switch between accounts to see or update them.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/leefowlercu/agent-kit/gtasks-todo-manager
Any agent
npx skills add leefowlercu/agent-kit --skill gtasks-todo-manager
Clone the repo
git clone --depth 1 https://github.com/leefowlercu/agent-kit

Made for: Claude Code, Codex.

Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,068 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00070 $0.01068
Opus 5 $0.00035 $0.00534
Sonnet 5 $0.00014 $0.00214
Haiku 4.5 $0.00007 $0.00107

Measured 2d ago against content hash bc8d448d6b36, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gtasks-todo-manager 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.

The scan reads SKILL.md. This mod also ships 19 executable files (scripts/cli.js, scripts/commands/accounts.js, scripts/commands/aggregate.js, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/gtasks-todo-manager/skills/gtasks-todo-manager/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

gtasks-todo-manager

Overview

This skill enables Claude Code agents to manage to-do items across multiple Google accounts through the Google Tasks API. It provides comprehensive task management including creating, updating, completing, and organizing tasks, as well as managing task lists and aggregating views across accounts.

The skill uses a BYOC (Bring Your Own Credentials) model where users provide their own Google Cloud OAuth credentials, ensuring security and privacy.

CLI Location

The CLI is located in the scripts subdirectory of this skill's base directory. When this skill is loaded, you receive a "Base directory for this skill" path. The CLI path is:

{base_directory}/scripts/cli.js

All CLI commands in this skill's documentation assume you are running them from the scripts directory or using the full path.

Before Any Operation

IMPORTANT: Before performing any operation with this skill, you MUST complete the following checks in order:

1. Verify Authentication

Always verify authentication first:

node scripts/cli.js auth validate

If this command fails, proceed to the Setup operation.

2. Check for Config Migrations

After authentication succeeds, check if the config needs migration:

cat ~/.config/gtasks-todo-manager/config.json | jq -r '.schemaVersion // "unversioned"'

Current schema version: 0.3.2

If the result is unversioned or an older version, proceed to the Migrations operation before continuing with the requested operation.

Operations

For common natural-language workflows, read the matching workflow reference first:

User Intent Workflow Reference
Set up OAuth credentials and authenticate accounts Setup Workflow
Add a task Add Task Workflow
Complete a task Complete Task Workflow
List or filter tasks List Tasks Workflow
Suggest tasks for today Today Workflow
List, create, rename, or delete task lists Task Lists Workflow
Show cross-account summary statistics Summary Workflow
Initialize a project task list Project Init Workflow
Show project task-list association Project Status Workflow

Read the full file on GitHub · 98 lines

Files

What ships with it

60 files 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.

Changes

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.

  1. 2d ago First seen · 98 lines · 70 tokens per session scan A bc8d448d6b36

Subscribe to this mod's changes

gtasks-todo-manager is a skill published in the GitHub repository leefowlercu/agent-kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 1,068 once invoked, about $0.0003 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-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens