Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jtprogru/bear-skills/plugin install bear-skillsWrote 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/jtprogru/bear-skills/srekit-postmortem)<a href="https://agentmods.dev/skills/jtprogru/bear-skills/srekit-postmortem"><img src="https://agentmods.dev/badge/skills/jtprogru/bear-skills/srekit-postmortem/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/jtprogru/bear-skills/srekit-postmortem"><img src="https://agentmods.dev/badge/skills/jtprogru/bear-skills/srekit-postmortem.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.00141 | $0.05209 |
| Opus 5 | $0.00071 | $0.02604 |
| Sonnet 5 | $0.00028 | $0.01042 |
| Haiku 4.5 | $0.00014 | $0.00521 |
Grade A, and why
srekit-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 8d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
srekit-postmortem
Скаффолдит постмортем через srekit postmortem и помогает заполнить его на основе того, что обсуждалось в текущей сессии.
Когда использовать
- Пользователь просит написать/оформить постмортем (любая формулировка).
- Пользователь начинает разбор инцидента и хочет файл-каркас, который дальше можно дописывать.
- Пользователь явно упоминает утилиту
srekit.
Никакого «исходного файла» (live-incident отчёта, INC-тикета, чат-лога) скилл не предполагает. Все данные для постмортема приходят из текущего разговора: что пользователь рассказал об инциденте, какие факты вы вместе зафиксировали, что видно в логах/коммитах. Если по какому-то полю данных в сессии нет — спрашивай у пользователя или ставь GAP-маркер; не выдумывай.
Что делает srekit postmortem
srekit postmortem — это локально установленная CLI-утилита, которая генерирует markdown-каркас постмортема в Google-SRE-стиле из встроенного (или кастомного) шаблона. Утилита не заполняет содержимое — она только готовит структуру с frontmatter (id, creation_date, severity, owner, …) и пустыми секциями.
Полный CLI-справочник: см. references/srekit-cli.md.
Ключевые флаги, которые ты будешь использовать:
| Флаг | Назначение |
|---|---|
-T, --title |
обязательный — заголовок инцидента |
--severity |
SEV-1 / SEV-2 / SEV-3 (по умолчанию SEV-3) |
--owner |
ответственный (всегда роль, не имя — см. ниже) |
--start |
начало в RFC3339 |
--end |
конец/mitigation в RFC3339 |
--out |
путь к выходному файлу |
--templates-dir |
one-shot override директории пользовательских шаблонов (на одну команду; иначе берётся из конфига) |
--force |
перезаписать существующий файл |
--dry-run |
напечатать в stdout, не писать на диск |
--from FILE |
прочитать секции из JSON (- для stdin) — round-trip workflow |
--schema |
вывести JSON Schema для --from входа |
--validate FILE |
валидировать input-файл без рендера |
--template FILE (one-shot подмена шаблона) у postmortem больше нет — удалён в v0.22.0. Кастомный шаблон подключается через --templates-dir (или через конфиг — templates_dir: в ~/.config/srekit/config.yaml / env SREKIT_TEMPLATES_DIR).
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 222 lines · 141 tokens per session scan A 880d02adb0b1
srekit-postmortem is a skill published in the GitHub repository jtprogru/bear-skills (1 stars, last pushed 21d ago), licensed MIT. It adds 141 tokens to every session and 5,209 once invoked, about $0.0007 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 skills, from other repositories
content-planner
GSC-driven content calendar. Pulls real Search Console data, finds the highest click-potential opportunities (striking-distance queries at positions 5-20, unanswered query intent, related-keyword expansions), and produces a dated, prioritized content calendar — ready to hand to /content-writer. Use when the user asks…
setup-cms
Connect a CMS to notfair SEO tools. Guides users through configuring WordPress, Strapi, Contentful, or Ghost — tests the connection, and writes credentials to .env.local. Once set up, seo-analysis automatically cross- references CMS content against Google Search Console data. Use whenever the user says "connect my…
broken-link-checker
Scans a website to find broken links (404s, 500s). Crawls internal pages, identifies broken outbound links, and reports source pages for easy fixing. Use this when the user asks to "check for broken links", "find 404s", "audit my links", or "is my site healthy".
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
google-ads-copy
Generate and A/B test Google Ads copy. Use when asked to write ad copy, headlines, descriptions, create ad variants, test ad messaging, improve CTR, or generate RSA (Responsive Search Ad) components. Trigger on "ad copy", "write ads", "headlines", "descriptions", "RSA", "responsive search ad", "ad text", "ad…
hreflang-international
International / multilingual SEO audit focused on hreflang correctness. Detects and diagnoses the most common (and ranking-damaging) hreflang mistakes: missing or broken return tags, wrong language/region codes, missing x-default, self-referencing errors, conflicts between hreflang and canonical, and inconsistent…