google-workspace-ops

google-workspace-ops is a skill for Claude Code, Codex from nklofy/code-agent-skills. It costs 59 tokens per session (596 once invoked), scanned A, a copy of google-workspace-ops, Apache-2.0.

A workflow for managing Google Drive, Docs, Sheets, and Slides together. It treats shared files as connected workspaces for documents, tables, presentations, and plans.

In plain words
What is it for?
Use it to find, summarize, edit, clean up, migrate, and organize Google Workspace documents, spreadsheets, presentations, trackers, and plans.
Why use it?
It avoids switching between disconnected file tasks and reduces mistakes caused by editing or restructuring shared files without inspecting them first.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to find, summarize, edit, clean up, migrate, and organize Google…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nklofy/code-agent-skills/google-workspace-ops
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.

Any agent
npx skills add nklofy/code-agent-skills --skill google-workspace-ops
Clone the repo
git clone --depth 1 https://github.com/nklofy/code-agent-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for google-workspace-ops

README.md
[![agentmods](https://agentmods.dev/badge/skills/nklofy/code-agent-skills/google-workspace-ops.svg)](https://agentmods.dev/skills/nklofy/code-agent-skills/google-workspace-ops)
Your own site
<a href="https://agentmods.dev/skills/nklofy/code-agent-skills/google-workspace-ops"><img src="https://agentmods.dev/badge/skills/nklofy/code-agent-skills/google-workspace-ops.svg" alt="Measured on agentmods" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 596 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 89% copy Near-identical to another mod 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.1 $0.00059 $0.00596
Opus 5 $0.00030 $0.00298
Sonnet 5 $0.00012 $0.00119
Haiku 4.5 $0.00006 $0.00060

Measured 3d ago against content hash 93ab16b44764, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

google-workspace-ops 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 3d 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.

Origin

This is a copy

89% identical to google-workspace-ops — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

affaan-m-ECC/google-workspace-ops/SKILL.md · 97 lines

How it starts

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

Google Workspace Ops

This skill is for operating shared docs, spreadsheets, and decks as working systems, not just editing one file in isolation.

When to Use

  • User needs to find a doc, sheet, or deck and update it in place
  • Consolidating plans, trackers, notes, or customer lists stored in Google Drive
  • Cleaning or restructuring a shared spreadsheet
  • Importing, repairing, or reformatting a Google Slides deck
  • Producing summaries from Docs, Sheets, or Slides for decision-making

Preferred Tool Surface

Use Google Drive as the entry point, then switch to the right specialist:

  • Google Docs for text-heavy docs
  • Google Sheets for tabular work, formulas, and charts
  • Google Slides for decks, imports, template migration, and cleanup

Do not guess structure from filenames alone. Inspect first.

Workflow

1. Find the asset

Start with the Drive search surface to locate:

  • the exact file
  • sibling assets
  • likely duplicates
  • recently modified versions

If several documents look similar, confirm by title, owner, modified time, or folder.

2. Inspect before editing

Before making changes:

  • summarize current structure
  • identify tabs, headings, or slide count
  • detect whether the task is local cleanup or structural surgery

Pick the smallest tool that can safely perform the work.

3. Edit with precision

  • For Docs: use index-aware edits, not vague rewrites
  • For Sheets: operate on explicit tabs and ranges
  • For Slides: distinguish content edits from visual cleanup or template migration

If the requested work is visual or layout-sensitive, iterate with inspection and verification instead of one giant blind update.

4. Keep the working system clean

When the file is part of a larger workflow, also surface:

  • duplicate trackers
  • outdated decks
  • stale docs vs canonical docs
  • whether the asset should be archived, merged, or renamed

Output Format

Use:

ASSET
- file name
- type
- why this is the right file

CURRENT STATE
- structure summary
- key problems or blockers

ACTION
- edits made or recommended

FOLLOW-UPS
- archive / merge / duplicate cleanup / next file to update

Read the full file on GitHub · 97 lines

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. 3d ago First seen · 97 lines · 59 tokens per session scan A 93ab16b44764

Subscribe to this mod's changes

google-workspace-ops is a skill published in the GitHub repository nklofy/code-agent-skills (18 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 596 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to google-workspace-ops, differing in 27 lines, and is treated as a copy.