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 skills add taslim/nanoclaw-gws-ea --skill google-docsgit clone --depth 1 https://github.com/taslim/nanoclaw-gws-eaWrote 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/taslim/nanoclaw-gws-ea/google-docs)<a href="https://agentmods.dev/skills/taslim/nanoclaw-gws-ea/google-docs"><img src="https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/google-docs/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/skills/taslim/nanoclaw-gws-ea/google-docs"><img src="https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/google-docs.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.00047 | $0.00421 |
| Opus 5.5 | $0.00019 | $0.00168 |
| Sonnet 5.5 | $0.00009 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
google-docs 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
Google Docs
Workflow
- Research and draft — do all research, outlining, and writing as a
.mdfile in/workspace/group/. Get the content right before touching Docs - Import to Google Doc — use
import_to_google_docwith the markdown file path (file:///workspace/group/xyz-draft.md). This converts headings, bold, italic, lists, tables, and links into native Google Docs formatting automatically - Share and link — share edit access with your principal's email, then send them the link
- Clean up — delete the local markdown file after successful import. If import fails, keep it so nothing is lost
Editing Existing Docs
For modifications after import, use the Docs tools directly:
modify_doc_text— insert/replace text with formatting (bold, italic, links, colors)update_paragraph_style— change headings, alignment, spacinginsert_doc_elements/create_table_with_data— add tables, lists, page breaks- Call
inspect_doc_structurefirst to get accurate character indices — they shift as you edit
What NOT to Do
- Don't use
create_docwith markdown content — it treats everything as literal plain text - Don't skip the markdown draft — writing directly into Docs with formatting tool calls is slow and error-prone
Verification
After creating a doc, silently verify:
- Headings render as headings, not literal
#characters - No raw formatting markers (
**,-,`) appear as visible text - Tables render as actual tables, not pipe-delimited text
- Doc is shared with your principal's email with edit access
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 · 35 lines · 47 tokens per session scan A f5e2b571f412
google-docs is a skill published in the GitHub repository taslim/nanoclaw-gws-ea (11 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 421 once invoked, about $0.0002 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-18.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
apify-youtube-transcript-scraper
Get YouTube captions, timestamped quotations, SRT/VTT and translated transcripts for videos, channels and playlists through the harshmaur/youtube-transcript-scraper Apify Actor.
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
baoyu-youtube-transcript
A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.