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 commands/bruno-rv/premium-presentations/present-postmortemgit clone --depth 1 https://github.com/bruno-rv/premium-presentationsWrote 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/commands/bruno-rv/premium-presentations/present-postmortem)<a href="https://agentmods.dev/commands/bruno-rv/premium-presentations/present-postmortem"><img src="https://agentmods.dev/badge/commands/bruno-rv/premium-presentations/present-postmortem.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.00037 | $0.02311 |
| Opus 5 | $0.00018 | $0.01156 |
| Sonnet 5 | $0.00007 | $0.00462 |
| Haiku 4.5 | $0.00004 | $0.00231 |
Grade A, and why
present-postmortem 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 3d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Turn a user-supplied incident document into a deck_doctor-green premium
deck grounded in that document — no invented timeline, no invented root
cause, no invented impact. This funnels into the existing
premium-presentations skill pipeline verbatim: new-deck.sh → spec →
generate → deck_doctor.py. Do not emit slides directly and do not
bypass the spec contract.
0. Set provider paths
Claude Code keeps the installed plugin immutable. Capture its bundled skill
from CLAUDE_PLUGIN_ROOT, and write every generated artifact beneath the
active project in CLAUDE_PROJECT_DIR:
plugin_root="${CLAUDE_PLUGIN_ROOT}"
if [ -z "$plugin_root" ]; then
echo "present-postmortem: CLAUDE_PLUGIN_ROOT is required" >&2
exit 1
fi
skill_root="$plugin_root/skills/premium-presentations"
project_root="${CLAUDE_PROJECT_DIR}"
if [ -z "$project_root" ]; then
echo "present-postmortem: CLAUDE_PROJECT_DIR is required" >&2
exit 1
fi
deck_root="$project_root/assets/decks"
themes_css="$project_root/assets/shared/premium-themes.css"
if [ ! -f "$themes_css" ]; then
themes_css="$skill_root/assets/shared/premium-themes.css"
fi
cd "$project_root"
The cd is deliberately after both roots are captured. All subsequent
commands use these absolute paths; do not substitute cwd-relative
skills/premium-presentations paths.
1. Parse and validate arguments (loud fail if the incident file is missing)
Argument contract:
/present-postmortem <incident-file> [--git-range <ref>..<ref>] [--ci-log <file>] [--keep-identifiers]
The incident file is required. Delegate parsing to the guard so spaces in paths, missing flag values, option-like values, and conflicting repeated flags are rejected deterministically rather than by fragile bash splitting:
if [ -z "$1" ]; then
echo "present-postmortem: an incident-file argument is required — /present-postmortem <incident-file> [--git-range <ref>..<ref>] [--ci-log <file>] [--keep-identifiers]" >&2
exit 1
fi
parsed_args="$(python3 "$skill_root/scripts/recipe_source_guard.py" check-args "$@")" || exit 1
incident_file="$(python3 -c 'import json,sys;print(json.loads(sys.argv[1])["incident_file"])' "$parsed_args")"
git_range="$(python3 -c 'import json,sys;v=json.loads(sys.argv[1])["git_range"];print(v or "")' "$parsed_args")"
ci_log="$(python3 -c 'import json,sys;v=json.loads(sys.argv[1])["ci_log"];print(v or "")' "$parsed_args")"
keep_identifiers="$(python3 -c 'import json,sys;print(json.loads(sys.argv[1])["keep_identifiers"])' "$parsed_args")"
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.
- 3d ago First seen · 211 lines · 37 tokens per session scan A acb8893c6903
present-postmortem is a command published in the GitHub repository bruno-rv/premium-presentations (3 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 2,311 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 commands, from other repositories
video
Records a pitch deck to WebM (Playwright recordVideo).
export
Export a pitch deck to PPTX, video, and/or speaker notes in one command.
morph-deck
Generate launch-video-style React presentations with shared-layout (FLIP) morph transitions. Subcommands: new, iterate, render, pptx, video, export. Use when the user asks for a pitch deck, launch video, demo storyboard, or any cinematic presentation.
pptx
Export the active morph-deck deck to PowerPoint .pptx with Morph transitions.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.