recipe-post-mortem-setup

recipe-post-mortem-setup is a skill for Claude Code, Codex from StreakYC/googleworkspacecli. It costs 28 tokens per session (306 once invoked), scanned A, a copy of recipe-post-mortem-setup, Apache-2.0.

A workflow for documenting a software or service incident in Google Docs, booking a review meeting in Google Calendar, and notifying a team in Google Chat.

In plain words
What is it for?
Use it after an incident to record the summary, timeline, root cause, and action items, then arrange a review and tell the team.
Why use it?
It keeps the incident record, review meeting, and team notification together so these follow-up tasks are not missed.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: built for openclaw.

Good fit Use it after an incident to record the summary, timeline, root cause, and action items, then arrange a review and tell the team.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/streakyc/googleworkspacecli/recipe-post-mortem-setup
Install

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.

Any agent
npx skills add StreakYC/googleworkspacecli --skill recipe-post-mortem-setup
Clone the repo
git clone --depth 1 https://github.com/StreakYC/googleworkspacecli

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for recipe-post-mortem-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/streakyc/googleworkspacecli/recipe-post-mortem-setup/github.svg)](https://agentmods.dev/skills/streakyc/googleworkspacecli/recipe-post-mortem-setup)
Your own site
<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/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for recipe-post-mortem-setup

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 306 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00306
Opus 5.5 $0.00011 $0.00122
Sonnet 5.5 $0.00006 $0.00061
Haiku 4.5 $0.00003 $0.00031

Measured 1mo ago against content hash 019a6f0c21d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

Origin

This is a copy

100% identical to recipe-post-mortem-setup — 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.

skills/recipe-post-mortem-setup/SKILL.md · 30 lines

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

  1. Create post-mortem doc: gws docs +write --title 'Post-Mortem: [Incident]' --body '## Summary\n\n## Timeline\n\n## Root Cause\n\n## Action Items'
  2. 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'
  3. Notify in Chat: gws chat +send --space spaces/ENG_SPACE --text '🔍 Post-mortem scheduled for [Incident].'
Changes

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.

  1. 1mo ago First seen · 30 lines · 28 tokens per session scan A 019a6f0c21d6

Subscribe to this mod's changes

recipe-post-mortem-setup is a skill published in the GitHub repository StreakYC/googleworkspacecli (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 306 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to recipe-post-mortem-setup, differing in 0 lines, and is treated as a copy.