Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/JustineDevs/premortemnpx agentmods add skills/justinedevs/premortem/migrating-to-zero-yamlWrote 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/migrating-to-zero-yaml)<a href="https://agentmods.dev/skills/justinedevs/premortem/migrating-to-zero-yaml"><img src="https://agentmods.dev/badge/skills/justinedevs/premortem/migrating-to-zero-yaml/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/migrating-to-zero-yaml"><img src="https://agentmods.dev/badge/skills/justinedevs/premortem/migrating-to-zero-yaml.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.00085 | $0.02618 |
| Opus 5 | $0.00043 | $0.01309 |
| Sonnet 5 | $0.00017 | $0.00524 |
| Haiku 4.5 | $0.00009 | $0.00262 |
Grade A, and why
migrating-to-zero-yaml 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrating to Zero YAML
This skill replaces the old CLI migrator with an LLM-driven mechanical migration. Keep behavior as close as possible to the existing YAML project, then validate and stop. Do not turn this into a broader cleanup unless the user asks.
Critical rule
- Do not tell the user to run
nango migrate-to-zero-yaml. - Perform the migration manually in code.
- Preserve existing behavior first.
- Do not opportunistically migrate
lastSyncDate,syncType,trackDeletes, or validation patterns unless the user asks or compilation forces you to touch them. - If the repo is already Zero YAML, stop and switch to a regular Zero YAML refactor workflow instead of forcing a migration.
Preconditions
- Confirm you are in the Nango project root and
nango.yamlexists. - Make sure there is a rollback path before destructive edits (git branch/commit or external backup).
- Read
nango.yamland inventory:- integrations
- syncs
- actions
- on-event handlers
- models
- Inspect the existing TypeScript files that those YAML entries point to.
- Keep the migration mechanical. Avoid redesigning APIs, renaming scripts, or changing business logic.
End state you are aiming for
The migrated project should have:
package.jsontsconfig.json- root
models.ts - root
index.ts - integration files exporting
createSync(),createAction(), orcreateOnEvent() - helper files importing Nango runtime types from
nango - no
nango.yamlin the final migrated state
Migration workflow
- Read
nango.yamland build a migration inventory. - Create or update Zero YAML scaffolding:
package.jsontsconfig.json
- Generate
models.tsfrom the YAML models. - Rewrite each sync file into
createSync(...). - Rewrite each action file into
createAction(...). - Rewrite each lifecycle handler into
createOnEvent(...). - Generate
index.tsside-effect imports for every migrated script. - Fix helper-file imports and small TypeScript breakages.
- Compile and validate.
- Remove
nango.yamlonly after the replacement project is in place and there is still a rollback path outside the file.
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 · 328 lines · 85 tokens per session scan A 2ed7312fd105
migrating-to-zero-yaml is a skill published in the GitHub repository JustineDevs/premortem (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 85 tokens to every session and 2,618 once invoked, about $0.0004 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.
azure-eventhub-dotnet
Azure Event Hubs SDK for .NET. Use for high-throughput event streaming: sending events (EventHubProducerClient, EventHubBufferedProducerClient), receiving events (EventProcessorClient with checkpointing), partition management, and real-time data ingestion. Triggers: "Event Hubs", "event streaming"…
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.
notion
Notion workspace integration for searching pages, managing databases, creating postmortems, and exporting RCA findings.
ak-add-integration
Add a messaging platform integration to an existing Agent Kernel project. This skill guides you through adding Slack, WhatsApp, Messenger, Instagram, Telegram, Teams, or Gmail integration by generating configuration, updating dependencies, and setting up webhook handlers. Designed for users extending their agents.