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/recipe-post-mortem-setupnpx skills add StreakYC/googleworkspacecli --skill recipe-post-mortem-setupgit 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/recipe-post-mortem-setup)<a href="https://agentmods.dev/skills/streakyc/googleworkspacecli/recipe-post-mortem-setup"><img src="https://agentmods.dev/badge/skills/streakyc/googleworkspacecli/recipe-post-mortem-setup.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 | $0.00028 | $0.00306 |
| Opus 5 | $0.00014 | $0.00153 |
| Sonnet 5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
recipe-post-mortem-setup 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 today.
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
Set Up Post-Mortem
PREREQUISITE: Load the following skills to execute this recipe:
gws-docs,gws-calendar,gws-chat
Create a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat.
Steps
- Create post-mortem doc:
gws docs +write --title 'Post-Mortem: [Incident]' --body '## Summary\n\n## Timeline\n\n## Root Cause\n\n## Action Items' - Schedule review meeting:
gws calendar +insert --summary 'Post-Mortem Review: [Incident]' --attendee [email protected] --start '2026-03-16T14:00:00' --end '2026-03-16T15:00:00' - Notify in Chat:
gws chat +send --space spaces/ENG_SPACE --text '🔍 Post-mortem scheduled for [Incident].'
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.
- today First seen · 30 lines · 28 tokens per session scan A 019a6f0c21d6
recipe-post-mortem-setup is a skill published in the GitHub repository StreakYC/googleworkspacecli (0 stars, last pushed 29d ago), licensed Apache-2.0. It adds 28 tokens to every session and 306 once invoked, about $0.0001 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-09-03.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…