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 JustineDevs/premortem --skill invariantgit clone --depth 1 https://github.com/JustineDevs/premortemWrote 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/justinedevs/premortem/invariant)<a href="https://agentmods.dev/skills/justinedevs/premortem/invariant"><img src="https://agentmods.dev/badge/skills/justinedevs/premortem/invariant/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/justinedevs/premortem/invariant"><img src="https://agentmods.dev/badge/skills/justinedevs/premortem/invariant.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.00052 | $0.00596 |
| Opus 5 | $0.00026 | $0.00298 |
| Sonnet 5 | $0.00010 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
invariant-guardrails 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 9d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invariant Guardrails (Premortem)
Invariant adds rule-based guardrails over agent traces: tool-call sequences, message content, and MCP flows. Premortem already ships lightweight input/output guardrails in @premortem/security; Invariant is the path for richer, policy-as-code rules when agent tool use expands.
Current repo boundary
| Layer | Location | Scope |
|---|---|---|
| Input/output string guardrails | packages/security/src/input-guardrail.ts, output-guardrail.ts |
Prompt injection terms, secret leakage |
| Invariant policies | Not runtime-wired yet | Future MCP/tool-call policy layer |
| Eval gate | pnpm run eval:prompts + promptfoo |
Prompt regression, not live proxy |
Do not assume Invariant Gateway is deployed. Treat this skill as design and policy authoring guidance until a gateway cutover is explicitly scoped.
When to use
- Authoring guardrail rules for tool-call sequences (e.g. block
send_emailafter untrustedget_website) - Reviewing agent blast radius before enabling new MCP tools
- Planning a proxy/gateway layer between orchestrator and external tools
- Complementing
$vet/llm-securitywith executable policy sketches
Rule shape (upstream)
raise "External email to unknown address" if:
(call: ToolCall) -> (call2: ToolCall)
call is tool:get_inbox
call2 is tool:send_email({ to: ".*@[^ourcompany.com$].*" })
See references/rule-writing.md for Premortem-oriented examples and integration notes.
Premortem integration path (phased)
- Now: Keep
@premortem/securityguardrails on all user-supplied and model output text. - Eval: Extend promptfoo suites in
packages/evals/for injection and tool-misuse fixtures. - Later: Run Invariant locally against orchestrator trace exports, or front MCP/LLM traffic with Invariant Gateway when tool surface grows.
Rules
- Authorization required for any red-team or live guardrail bypass testing. Use
llm-securityworkflows. - Prefer deterministic repo guardrails for simple injection patterns; use Invariant rules for multi-step tool graphs.
- Document accepted risks when a rule is deferred, same as
$vetoutput contract.
What ships with it
1 file 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.
- 9d ago First seen · 54 lines · 52 tokens per session scan A 539579e43cc1
invariant-guardrails is a skill published in the GitHub repository JustineDevs/premortem (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 596 once invoked, about $0.0003 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
awesome-azd-template-submit
Submit an azd template to the awesome-azd gallery. Use when asked to submit, add, or contribute a template to awesome-azd. Requires only a GitHub repository URL — all metadata (title, description, languages, frameworks, Azure services, IaC) is auto-detected by the submission pipeline.
azure-cli
Use the Azure CLI to manage subscriptions, resource groups, AKS, App Service, Key Vault, and role assignments.
bitbottle
Reference for the bitbottle CLI — a gh-style tool for Bitbucket Server/DC and Cloud. Load when the user asks about bitbottle commands, auth setup, PRs, repos, branches, tags, commits, pipelines, or why a command failed. Load even if the user just says "bitbottle", mentions "Bitbucket", or pastes a bitbottle error…
azure-cli
A command-line tool for managing Microsoft Azure, Microsoft's cloud platform, from a terminal. It covers account sign-in, subscriptions, resource groups, virtual machines, and other cloud resources.
extract-api
This skill should be used when the user asks to "extract API from", "import API from", "add commands from this repo", "register API from docs", "convert docs to CLI commands", "import Postman collection", or provides a GitHub repository URL, a documentation site URL, a Postman collection file/URL, or a local API…
sidekick
ALWAYS run sdkck search FIRST before using ANY tool, MCP server, Bash command, or external API. sdkck is the canonical command surface for Jira, Sentry, MySQL, Postgres, Supabase, Bitbucket, Confluence, and imported OpenAPI/Postman specs. Trigger on every task involving external systems, APIs, databases, tickets…