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/googleworkspace/cli/gws-workflow-weekly-digestnpx skills add googleworkspace/cli --skill gws-workflow-weekly-digestgit clone --depth 1 https://github.com/googleworkspace/cliWrote 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/skills/googleworkspace/cli/gws-workflow-weekly-digest)<a href="https://agentmods.dev/skills/googleworkspace/cli/gws-workflow-weekly-digest"><img src="https://agentmods.dev/badge/skills/googleworkspace/cli/gws-workflow-weekly-digest.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 | $0.00023 | $0.00307 |
| Opus 5 | $0.00012 | $0.00153 |
| Sonnet 5 | $0.00005 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
gws-workflow-weekly-digest 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 4d 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- gws-workflow-weekly-digest — 100% identical, 0 lines differ
- gws-workflow-weekly-digest — 100% identical, 0 lines differ
- gws-workflow-weekly-digest — 100% identical, 0 lines differ
- gws-workflow-weekly-digest — 94% identical, 5 lines differ
What it actually says
workflow +weekly-digest
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
Weekly summary: this week's meetings + unread email count
Usage
gws workflow +weekly-digest
Flags
| Flag | Required | Default | Description |
|---|---|---|---|
--format |
— | — | Output format: json (default), table, yaml, csv |
Examples
gws workflow +weekly-digest
gws workflow +weekly-digest --format table
Tips
- Read-only — never modifies data.
- Combines calendar agenda (week) with gmail triage summary.
See Also
- gws-shared — Global flags and auth
- gws-workflow — All cross-service productivity workflows commands
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.
- 4d ago First seen · 48 lines · 23 tokens per session scan A 6ece4c91d181
gws-workflow-weekly-digest is a skill published in the GitHub repository googleworkspace/cli (30,712 stars, last pushed 8d ago), licensed Apache-2.0. It adds 23 tokens to every session and 307 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-08-30.
Other skills, from other repositories
wiki-aggregate
Use when you have N≥3 raw research artifacts (notes, podcast summaries, deep-research dumps, daily intel, paper analyses) on one topic and want to lift them into a single structured pack with cross-source claims and provenance — instead of one-shot summarization that loses 90% of intermediate evidence. Treats the N…
save-handoff
Save a concise handoff summary only when the user explicitly requests it. Use this for resumable progress notes in generic agent environments where a real session importer is not guaranteed.
authoring-error-tracking-alerts
Author error tracking alerts that fire when an issue is created, reopened, or starts spiking. Use when the user asks to set up error notifications, route exceptions to Slack/webhook/Linear, or evaluate which error events are worth alerting on. Covers trigger-event selection, integration choice, dedup against existing…
creating-ai-subscription
Create a recurring AI-generated PostHog report — schedule a free-text prompt to run on a cron, with the LLM-synthesized markdown delivered to email or Slack on each tick. Use when the user wants a recurring AI summary of X on any cadence (daily, weekly, monthly, yearly) rather than a one-off report. (To attach an AI…
designing-email-templates
Author, save, and edit email templates in the PostHog workflows library — compose email design JSON with Liquid personalization and create and round-trip-edit templates over MCP. Use when asked to design, build, update, or fix an email template for workflows, broadcasts, or campaigns.
manage-calendar-google-microsoft
Connect Google or Microsoft calendar, contacts, and Google Chat, and configure Voice Logica appointment settings. Use when the user wants bookings, availability, contacts, Outlook, Meet, or Chat on an agent.