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 pbc-os/smb-starter-kit --skill google-chatgit clone --depth 1 https://github.com/pbc-os/smb-starter-kitWrote 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/pbc-os/smb-starter-kit/google-chat)<a href="https://agentmods.dev/skills/pbc-os/smb-starter-kit/google-chat"><img src="https://agentmods.dev/badge/skills/pbc-os/smb-starter-kit/google-chat.svg" alt="Measured on agentmods" 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.00038 | $0.02152 |
| Opus 5 | $0.00019 | $0.01076 |
| Sonnet 5 | $0.00008 | $0.00430 |
| Haiku 4.5 | $0.00004 | $0.00215 |
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 8d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Chat
Team messaging for small businesses using Google Workspace.
Uses the gws CLI for all Chat operations. See the google-workspace skill for setup. For platform-agnostic team messaging best practices, see SMB Team Messaging — it applies to both Google Chat and Slack.
Triggers
- "send a chat message"
- "post to [space/channel]"
- "message the team"
- "set up chat spaces"
- "post an update"
- Any request involving Google Chat spaces or messages
Prerequisites
gwsCLI installed and authenticated with Chat scope- Run
gws auth login -s chatif not already done - Google Workspace account (Chat is not available on free Gmail)
Core Commands
# Send a message to a space
gws chat +send
# List spaces you're in
gws chat spaces list
# Get space details
gws chat spaces get --params '{"name": "spaces/SPACE_ID"}'
# List messages in a space
gws chat spaces messages list --params '{"parent": "spaces/SPACE_ID"}'
# Create a message
gws chat spaces messages create \
--params '{"parent": "spaces/SPACE_ID"}' \
--json '{"text": "Your message here"}'
# Reply in a thread
gws chat spaces messages create \
--params '{"parent": "spaces/SPACE_ID"}' \
--json '{"text": "Thread reply", "thread": {"name": "spaces/SPACE_ID/threads/THREAD_ID"}}'
SMB Space Structure
Recommended spaces for small businesses
| Space | Purpose | Who's In | Agent Posts |
|---|---|---|---|
| Daily Briefing | Morning digest + EOD summary | Everyone | Automated daily |
| General | Company-wide announcements | Everyone | Major alerts only |
| Orders | Order updates, fulfillment | Ops team | Order alerts |
| Sales | Revenue, transactions, wins | Leadership | Daily numbers |
| Inventory | Stock levels, vendor orders | Purchasing + ops | Low stock alerts |
| Ops Log | Shift notes, equipment, facilities | Ops team | Shift reminders |
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.
- 8d ago First seen · 238 lines · 38 tokens per session scan A cbd31ad0eea9
google-chat is a skill published in the GitHub repository pbc-os/smb-starter-kit (10 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 2,152 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-31.
Other skills, from other repositories
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
slack-tools
Slack workspace management and automation specialist.
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…