CWC Workshops is a collection of materials from Anthropic-run workshops on building and evaluating AI-assisted coding workflows. The workshops cover model selection, multi-agent systems, managed agents, and product development with coding agents. The catalogue entries are examples and teaching materials from those workflows.
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 anthropics/cwc-workshops --skill postmortem-reportgit clone --depth 1 https://github.com/anthropics/cwc-workshopsWrote 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/anthropics/cwc-workshops/postmortem-report)<a href="https://agentmods.dev/skills/anthropics/cwc-workshops/postmortem-report"><img src="https://agentmods.dev/badge/skills/anthropics/cwc-workshops/postmortem-report/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.
<a href="https://agentmods.dev/skills/anthropics/cwc-workshops/postmortem-report"><img src="https://agentmods.dev/badge/skills/anthropics/cwc-workshops/postmortem-report.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.00427 |
| Opus 5.5 | $0.00018 | $0.00171 |
| Sonnet 5.5 | $0.00009 | $0.00085 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
postmortem-report 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- postmortem-report — 100% identical, 0 lines differ
What it actually says
Postmortem report
You build the PDF yourself, in your sandbox. There is no template. Design it so a director understands the event in one minute and an engineer can check every claim.
What it must contain
- A headline and a summary of three or four sentences.
- A table of pages: page id, service, root cause. Pages that share a root cause are one incident; mark the others as symptoms.
- At least one chart drawn from real data. Compute it in your script from
/mnt/session/uploads/app.log(for example p99 latency or error rate per minute for each paged service) and mark the deploys on it. - For each root cause: a timeline in UTC, the evidence that proves it, what was ruled out, and the fix.
- Action items, each with an owner team and a priority.
How to build it
- Python with matplotlib and pandas is installed.
matplotlib.backends.backend_pdf.PdfPageswrites multi-page PDFs. pandoc and LaTeX are there too. Use whichever you can do fastest. - The investigators' findings are in
/workspace/findings/*.json. Start from those instead of investigating again. - Save the result to
/mnt/session/outputs/postmortem.pdf. Only files under/mnt/session/outputs/reach the user. - Be quick: write one script, run it, and fix it only if it errors. Two to four pages. Do not render the PDF to images to inspect it.
- Keep everything inside the page margins: wrap the title and any long table cell instead of letting it run off the edge.
- Follow any postmortem conventions you find in team memory.
When it is built, tell the user the file name in one or two sentences. Do not paste the report into the chat.
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.
- 6d ago First seen · 28 lines · 44 tokens per session scan A cc5d26aff129
postmortem-report is a skill published in the GitHub repository anthropics/cwc-workshops (2,210 stars, last pushed 6d ago), licensed Apache-2.0. It adds 44 tokens to every session and 427 once invoked, about $0.0002 per session on Opus 5.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-10-17.
Other skills, from other repositories
apify-youtube-transcript-scraper
Get YouTube captions, timestamped quotations, SRT/VTT and translated transcripts for videos, channels and playlists through the harshmaur/youtube-transcript-scraper Apify Actor.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
meta-web-to-pdf-briefing
Render a topic into a distributable PDF briefing in three steps: web search → bullet summary → styled PDF. Trigger when the user asks for a PDF briefing on a single topic.
pkf-writing
Author, update, convert, validate, persist, and render PKF (.pkf) content through message-inline, Library Asset, or Memory Page carriers. Use for structured reports, knowledge pages, delivery cards, or any .pkf body. NOT for recall, memory-graph placement, or curation decisions — those belong to the memory skill.
chat-complex-documents
Chat with and search your complex documents — ask questions, extract tables and fields, and get answers grounded in the source. Connects the hosted Unstructured Transform MCP server to parse, structure, and enrich PDFs, Word/Excel/PowerPoint, images, scanned files, emails, and 60+ other formats into clean, AI-ready…