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.
git clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/gws-tasks)<a href="https://agentmods.dev/commands/fakoli/fakoli-plugins/gws-tasks"><img src="https://agentmods.dev/badge/commands/fakoli/fakoli-plugins/gws-tasks/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/fakoli/fakoli-plugins/gws-tasks"><img src="https://agentmods.dev/badge/commands/fakoli/fakoli-plugins/gws-tasks.svg" alt="Reviewed on agentmods" width="80" 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.00010 | $0.00394 |
| Opus 5.5 | $0.00004 | $0.00158 |
| Sonnet 5.5 | $0.00002 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
gws-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 1mo 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
/gws-tasks
Manage Google Tasks using the gws CLI.
Instructions
When this command is invoked, parse $ARGUMENTS to determine the operation.
Common Operations
List task lists:
gws tasks tasklists list --format table
List tasks in default list:
gws tasks tasks list --params '{"tasklist": "@default"}' --format table
Create a task:
gws tasks tasks insert --params '{"tasklist": "@default"}' --json '{"title": "Task title", "notes": "Details"}'
Create a task with due date:
gws tasks tasks insert --params '{"tasklist": "@default"}' --json '{"title": "Task title", "due": "2026-03-20T00:00:00Z"}'
Complete a task:
gws tasks tasks patch --params '{"tasklist": "@default", "task": "TASK_ID"}' --json '{"status": "completed"}'
Delete a task:
gws tasks tasks delete --params '{"tasklist": "@default", "task": "TASK_ID"}'
Tips
- Due dates must be in RFC 3339 format (e.g.,
2026-03-20T00:00:00Z). - Task status values:
needsAction(open),completed. - Use
--dry-runbefore delete operations.
Error Handling
- Exit code 2: Auth expired. Tell user to run
gws auth login.
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.
- 1mo ago First seen · 56 lines · 10 tokens per session scan A b6270d03254c
gws-tasks is a command published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 29d ago), licensed MIT. It adds 10 tokens to every session and 394 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
optimize
Run the credo optimisation audit for the current repo: a freshness check, then a read-only scan (conflict hotspots, changelog fragments, test-stage convention, dogma settings, parallelism readiness, and - only if the user says Yes when asked before the scan - instruction consistency across the global and repo…
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
project
A command-style entry point for initializing a project with an interview, custom agents, skill workflows, and project instruction files. It also supports update, evolution, and diagnostic modes.
update-docs
Scan recently modified files and update the matching documentation.
update
You are executing the /import:update command. Re-fetch documentation from original sources.
explain
Explain the subject in depth using the fixed four-part structure: What, Why, Example, Consequences. Treat the subject as the thing to be explained, not as a literal question.