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/xiaomimimo/mimo-code/report-to-google-docnpx skills add XiaomiMiMo/MiMo-Code --skill report-to-google-docgit clone --depth 1 https://github.com/XiaomiMiMo/MiMo-CodeWhat 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.00042 | $0.01494 |
| Opus 5 | $0.00021 | $0.00747 |
| Sonnet 5 | $0.00008 | $0.00299 |
| Haiku 4.5 | $0.00004 | $0.00149 |
Grade A, and why
report-to-google-doc 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report To Google Doc
Use this skill only when the user explicitly needs a shareable Google Drive document from an existing HTML analytics report. The source must be an HTML report: a local file, a downloaded blob-hosted report, or a report produced by $build-report
HTML mode or an equivalent local portable report source.
The expected path is HTML -> DOCX -> Drive upload. It is acceptable for Drive to host the upload as a DOCX-backed viewer file rather than a native Google Docs MIME type. Do not use the old Google Docs batch-update request path.
Workflow
-
Resolve the HTML report.
Use an absolute local path. If the user provides a remote report, retrieve it first and pass the local HTML file to the helper. If the file is a sign-in page, redirect page, or tiny stub, stop and obtain the real report.
-
Run the bundled helper.
python3 <REPORT_TO_GOOGLE_DOC_SKILL_DIR>/scripts/report_to_google_doc_plan.py \ /absolute/path/to/report.html \ --out-dir /tmp/report_to_google_doc_planOmit
--render-workerson the normal path. Only pass a worker count after benchmarking the same report family locally. If dependencies are missing, use a local virtual environment withbeautifulsoup4,pillow, andpython-docx;cairosvgor headless Playwright are optional renderers. -
Inspect helper outputs.
Required outputs:
skeleton.txt: source text with stable placeholdersmanifest.json: parsed headings, tables, callouts, lists, styles, links, and rendered visual inventorypreflight_checks.json: source, width, DOCX, and rendered-image checksreport.docx: generated local Word documentdocx_upload_plan.json: compact upload instructionsplaceholder_queries.json: source mapping debug labels
Do not upload until
preflight_checks.jsonhasstatus: "passed"with zero errors. Warnings must either be fixed or called out in the handoff. -
Upload the DOCX.
mcp__codex_apps__google_drive._upload_file({ "file_uri": "/tmp/report_to_google_doc_plan/report.docx", "file_name": "Report Name.docx", "mime_type": "application/vnd.openxmlformats-officedocument.wordprocessingml.document" })
What ships with it
13 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.
- agents/openai.yaml 304 B
- scripts/report_to_google_doc_plan.py 212 B runs code
- scripts/report_to_google_doc/__init__.py 45 B runs code
- scripts/report_to_google_doc/cli.py 1.9 KB runs code
- scripts/report_to_google_doc/constants.py 2.1 KB runs code
- scripts/report_to_google_doc/docx_writer.py 12 KB runs code
- scripts/report_to_google_doc/html_parser.py 28 KB runs code
- scripts/report_to_google_doc/model.py 1017 B runs code
- scripts/report_to_google_doc/plan.py 4.6 KB runs code
- scripts/report_to_google_doc/quality.py 14 KB runs code
- scripts/report_to_google_doc/rendering.py 23 KB runs code
- scripts/report_to_google_doc/table_utils.py 1.5 KB runs code
- scripts/report_to_google_doc/utils.py 355 B runs code
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 · 113 lines · 42 tokens per session scan A 30c8a78135f0
report-to-google-doc is a skill published in the GitHub repository XiaomiMiMo/MiMo-Code (12,923 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,494 once invoked, about $0.0002 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
xiaomi-tts
Use this skill when the user wants to convert text to speech using Xiaomi MiMo's TTS models (mimo-v2.5-tts). Uses OpenAI-compatible chat/completions API with audio response. Supports multiple preset voices and custom voice design. Use when 用户提到 语音合成、文字转语音、TTS、朗读、读出来、生成语音、 生成音频、文本转音频、配音、念出来、小米语音、MiMo 语音、小米 TTS。.
byok-custom-model
Register a custom LLM endpoint with your own API key for chat in Starchild. Use when adding a personal Anthropic, OpenAI, Grok, Qwen, DeepSeek, Meta (Muse Spark), NEAR AI, or Venice key as a chat model (e.g. add my Claude key, register DeepSeek, use Muse Spark 1.1).
deepseek-vision
MUST use when the user sends or asks about images, photos, screenshots, pictures, audio, video, or mixed media documents, including requests to OCR/read text from an image. Route all media through Xiaomi MiMo V2.5 (mimo-v2.5) and mimo-v2.5-asr via scripts/mimo.py; never use local OCR, viewimage, native vision…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.