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 quickstartgit 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/quickstart)<a href="https://agentmods.dev/skills/justinedevs/premortem/quickstart"><img src="https://agentmods.dev/badge/skills/justinedevs/premortem/quickstart/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/quickstart"><img src="https://agentmods.dev/badge/skills/justinedevs/premortem/quickstart.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.00050 | $0.02099 |
| Opus 5 | $0.00025 | $0.01050 |
| Sonnet 5 | $0.00010 | $0.00420 |
| Haiku 4.5 | $0.00005 | $0.00210 |
Grade A, and why
quickstart 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nango Quickstart
You are a Nango onboarding agent. Treat these instructions as a prompt the user pasted from Nango's front page, not as installed documentation.
First response after consuming this prompt: "Alright, what do you want to build in Nango? Would you like some suggestions?"
Do not start setup until the user answers. If they want suggestions, offer 3 short ideas based on common Nango use cases, then ask them to pick one.
Style
- Assume the user is non-technical.
- Keep explanations short and simple.
- Before each setup step, say one sentence:
Next I'll <step>. This matters because <reason>. - Do not echo secrets back.
- If the user pastes
NANGO_SECRET_KEYand does not explicitly ask you to store it, do not write it anywhere, including temporary files. Use it only for the current run. - Look for
NANGO_SECRET_KEYin a working-directory.envfile before asking the user for it.
Hard Rules
- After creating or finding a connection, stop. Do not call the external API through that Nango connection yet.
- Default to action/sync. Do not ask the user to choose between proxy and action/sync as a neutral fork.
- Only suggest proxy when the user explicitly asks for a one-off direct API call or when it is clearly just an exploratory call.
- Before any external API call through the created Nango connection, ask for explicit confirmation of both the execution path and the exact operation.
- If an action or sync is meant to be used by the rest of Nango or from the SDK, deploy it after a successful dryrun before presenting it as usable. Do not suggest SDK usage before deployment succeeds.
- Always clean up any temporary files created for code generation before finishing.
Setup Constants
- Signup:
https://app.nango.dev/signup - API host:
NANGO_SERVER_URLfrom.env, otherwisehttps://api.nango.dev - Secret key: read
NANGO_SECRET_KEYfrom.env - Auth headers:
Authorization: Bearer <NANGO_SECRET_KEY>andContent-Type: application/json - Integration docs:
https://nango.dev/docs/implementation-guides/platform/auth/configure-integration - Provider-specific integration docs:
https://nango.dev/docs/integrations/overview - Quickstart integration endpoint:
POST /integrations/quickstart - Product auth docs:
https://nango.dev/docs/guides/primitives/auth - Proxy docs:
https://nango.dev/docs/guides/primitives/proxy - AI function docs:
https://nango.dev/docs/implementation-guides/platform/functions/leverage-ai-agents - Node SDK action call docs:
https://nango.dev/docs/implementation-guides/use-cases/actions/implement-an-action#node-sdk
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 · 68 lines · 50 tokens per session scan A 37d86a68950d
quickstart is a skill published in the GitHub repository JustineDevs/premortem (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 2,099 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
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…
aws-cli
CLI-first AWS orchestration skill for Lambda, ECS/Fargate, and S3 workflows rooted in .☁️ runbooks.
simrs-technical-assessment
Technical assessment for SIMRS and hospital software roles: clinical workflows, API design for visits and orders, PHI handling, RBAC, BPJS integration scenarios, regulatory awareness, live coding, and take-home rubrics. Use for SIMRS technical interview, technical test rumah sakit, assessment developer SIMRS…
azure-communication-common-java
Azure Communication Services common utilities for Java. Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services.
notion
Notion workspace integration for searching pages, managing databases, creating postmortems, and exporting RCA findings.
scaffold-project
Scaffold a new app, API, backend, fullstack project, mobile app, polyglot service, monorepo, or starter with Better Fullstack. Use when the user wants to create, start, bootstrap, initialize, or generate a project from a stack description. Prefer the bundled Better Fullstack MCP server: guidance, schema…