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/emdashcodes/claude-code-plugins/google-docs-readernpx skills add emdashcodes/claude-code-plugins --skill google-docs-readergit clone --depth 1 https://github.com/emdashcodes/claude-code-pluginsWhat 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.00065 | $0.01923 |
| Opus 5 | $0.00032 | $0.00962 |
| Sonnet 5 | $0.00013 | $0.00385 |
| Haiku 4.5 | $0.00006 | $0.00192 |
Grade C, and why
google-docs-reader scanned grade C with 1 finding 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.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/gdoc_exports/ How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Docs Reader
Overview
Read and analyze Google Workspace documents (Docs, Sheets, Slides) without direct API access. This skill exports Google Drive documents to local formats by opening export URLs in the browser, monitoring the Downloads folder, and moving files to a temporary directory for processing.
When to Use This Skill
Activate this skill when users ask to:
- Read or summarize Google Docs, Sheets, or Slides
- Extract content from Google Drive URLs
- Analyze
.gdoc,.gsheet, or.gslidesfiles from Google Drive File Stream/Desktop - Process multiple Google Workspace documents
Example user requests:
- "Read this Google Doc and summarize it: https://docs.google.com/document/d/ABC123/edit"
- "What's in this spreadsheet?" (pointing to a
.gsheetfile) - "Analyze the data in this Google Sheets URL"
- "Convert this Google Slides to markdown"
How It Works
The skill uses a browser-based export workflow:
- Extract document ID from URL or
.gdoc/.gsheet/.gslidesfile - Determine document type (Docs, Sheets, or Slides)
- Build export URL with appropriate format (DOCX, XLSX, PPTX)
- Open URL in browser (leverages existing Google account session)
- Monitor Downloads folder for the downloaded file
- Move to temp directory (
/tmp/gdoc_exports/) - Process with document skills (docx, xlsx, pptx skills)
- Clean up temporary file after reading
Export Formats
- Google Docs → DOCX (Microsoft Word format)
- Google Sheets → XLSX (Microsoft Excel format)
- Google Slides → PPTX (Microsoft PowerPoint format)
Reading Google Docs
Complete Workflow (Export + Read)
The simplest approach is to use both scripts together:
# 1. Export the Google Doc
EXPORTED=$(python3 ${CLAUDE_PLUGIN_ROOT}/skills/google-docs-reader/scripts/export_gdoc.py "<google-drive-url-or-file>")
# 2. Read the exported file
python3 ${CLAUDE_PLUGIN_ROOT}/skills/google-docs-reader/scripts/read_exported_doc.py "$EXPORTED"
What ships with it
3 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.
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.
- 2d ago First seen · 274 lines · 65 tokens per session scan C 4df608b38851
google-docs-reader is a skill published in the GitHub repository emdashcodes/claude-code-plugins (13 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,923 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
general-video
Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
mintlify-preview
Run the public Mintlify product docs site locally for live preview. Use when previewing or iterating on docs under docs/ (.mdx/.md pages, docs.json nav), or when the user says "start the docs", "run mintlify", "preview the docs site".