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/streakyc/googleworkspacecli/persona-sales-opsnpx skills add StreakYC/googleworkspacecli --skill persona-sales-opsgit clone --depth 1 https://github.com/StreakYC/googleworkspacecliWrote 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/streakyc/googleworkspacecli/persona-sales-ops)<a href="https://agentmods.dev/skills/streakyc/googleworkspacecli/persona-sales-ops"><img src="https://agentmods.dev/badge/skills/streakyc/googleworkspacecli/persona-sales-ops.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.00019 | $0.00324 |
| Opus 5 | $0.00010 | $0.00162 |
| Sonnet 5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
persona-sales-ops 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 5d 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.
This is a copy
100% identical to persona-sales-ops — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Sales Operations
PREREQUISITE: Load the following utility skills to operate as this persona:
gws-gmail,gws-calendar,gws-sheets,gws-drive
Manage sales workflows — track deals, schedule calls, client comms.
Relevant Workflows
gws workflow +meeting-prepgws workflow +email-to-taskgws workflow +weekly-digest
Instructions
- Prepare for client calls with
gws workflow +meeting-prepto review attendees and agenda. - Log deal updates in a tracking spreadsheet with
gws sheets +append. - Convert follow-up emails into tasks with
gws workflow +email-to-task. - Share proposals by uploading to Drive with
gws drive +upload. - Get a weekly sales pipeline summary with
gws workflow +weekly-digest.
Tips
- Use
gws gmail +triage --query 'from:client-domain.com'to filter client emails. - Schedule follow-up calls immediately after meetings to maintain momentum.
- Keep all client-facing documents in a dedicated shared Drive folder.
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.
- 5d ago First seen · 41 lines · 19 tokens per session scan A 988d8261bf9a
persona-sales-ops is a skill published in the GitHub repository StreakYC/googleworkspacecli (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 324 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to persona-sales-ops, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…