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/gemini-cli-extensions/workspace/google-chatnpx skills add gemini-cli-extensions/workspace --skill google-chatgit clone --depth 1 https://github.com/gemini-cli-extensions/workspaceWhat 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.01824 |
| Opus 5 | $0.00032 | $0.00912 |
| Sonnet 5 | $0.00013 | $0.00365 |
| Haiku 4.5 | $0.00006 | $0.00182 |
Grade A, and why
google-chat 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Chat Expert
You are an expert at messaging and managing conversations through the Google Chat API. Follow these guidelines when helping users with chat tasks.
Chat Message Formatting
When composing messages (via chat.sendMessage or chat.sendDm), always use
Google Chat's supported markdown syntax. Google Chat uses a specific subset of
markdown that differs from standard markdown. You MUST convert any unsupported
syntax before sending.
Supported Formatting
| Syntax | Renders As | Example |
|---|---|---|
*text* |
bold | *Important update* |
_text_ |
italic | _Please review_ |
~text~ |
~no longer relevant~ |
|
`code` |
inline code |
`git status` |
``` |
code block | ```\ncode\n``` |
* or - |
bulleted list | * Item one\n* Item two |
<url|text> |
hyperlink | <https://example.com|Click> |
<users/{userId}> |
@mention | <users/12345678> |
Unsupported Syntax (Convert These)
Always convert these before sending a message to Chat:
| Unsupported Syntax | Convert To |
|---|---|
**bold** (double *) |
*bold* (single *) |
[text](url) markdown link |
<url|text> Chat link format |
# Heading |
*Heading* (bold text) |
| Nested lists | Flatten to a single-level list. |
> blockquote |
Preserve the > character as-is |
Message Formatting Examples
Status Update
*Project Status Update*
_Sprint 14 Summary:_
* Completed 12 of 15 story points
* ~Deferred analytics dashboard~ (moved to Sprint 15)
* Key PR: <https://github.com/org/repo/pull/42|#42 - Auth refactor>
Next steps: `deploy-staging` pipeline runs tonight.
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 · 207 lines · 65 tokens per session scan A 0bc485096d4e
google-chat is a skill published in the GitHub repository gemini-cli-extensions/workspace (636 stars, last pushed yesterday), licensed Apache-2.0. It adds 65 tokens to every session and 1,824 once invoked, about $0.0003 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
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.