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 orwa-mahmoud/nightshift/plugin install nightshiftWrote 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/orwa-mahmoud/nightshift/start)<a href="https://agentmods.dev/skills/orwa-mahmoud/nightshift/start"><img src="https://agentmods.dev/badge/skills/orwa-mahmoud/nightshift/start.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.1 | $0.00023 | $0.02983 |
| Opus 5 | $0.00012 | $0.01491 |
| Sonnet 5 | $0.00005 | $0.00597 |
| Haiku 4.5 | $0.00002 | $0.00298 |
Grade A, and why
start 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 today.
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.
Start a Nightshift run in the host-opened project.
Resolve the installed plugin root to an absolute $NIGHTSHIFT_PLUGIN_ROOT — ${CLAUDE_PLUGIN_ROOT}
on Claude Code, $PLUGIN_ROOT on Codex when set, otherwise the absolute path this skill was
attached from (skills/start/SKILL.md). Run every command below through
"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns" — native Windows: & "$NIGHTSHIFT_PLUGIN_ROOT\runtime\windows\ns.ps1"
in the PowerShell tool, same verbs — which resolves the host and the workspace; ns help lists the
verbs, and ns bind prints the six resolved facts (TASK_ROOT, NIGHTSHIFT_WORKSPACE, NS,
NIGHTSHIFT_PLUGIN_ROOT, HOST, SOURCE); $NS below is that NS. Never a bare relative path: the working
directory persists between calls.
When a verdict names your host — permission modes, resume commands, the sandbox and identity
rules that belong to it — open
$NIGHTSHIFT_PLUGIN_ROOT/skills/nightshift/references/hosts/<host>.md for the host you are on,
and no other. Not before a verdict names it.
1. Preflight — one helper, one verdict per line
With work in the punch list, this command asks nothing. It reads the list, arms the site and works — which is what lets cron run it at 04:00 and lets the watchman revive it after a crash. It promotes nothing on its own: what is in the punch list is the shift, exactly as the owner left it.
The one time it speaks is when the punch list is empty. Then there is no work to do silently, so it looks at staged drafts and pending Hunt orders and asks which to promote.
"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns" start-preflight --host claude
Pass the host you are actually running on (claude, codex, or cursor). Every line it prints is
one verdict, and it explains itself:
ok <topic> <detail>— a resolved fact. Report it if the owner asked; otherwise continue.warn <topic> <detail>— say it once in plain English, then arm anyway. The choice stays the owner's.refuse <topic> <detail>— do not arm. Print theexplainandrepairlines that follow it verbatim and stop.
Exit status 0 means the shift may arm; non-zero is a refusal; 2 is a usage error in the call you
just made. An explain line says what the verdict means and a repair line is the exact action —
relay them, do not restate them, and never invent an explanation the helper did not print.
Two rules are policy rather than mechanics, so they are yours to hold whatever a verdict says:
never kill a live watchman and never start a second shift beside one; and never clear STOP or
invent a time budget for a paused shift whose deadline has passed.
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.
- today Changed · -119 lines · -18 tokens per session 190c284ce54b
- yesterday Changed · -51 lines scan B → A 9fca86f13aad
- 4d ago Changed · -2 lines 0251dcae7d64
- 8d ago First seen · 394 lines · 41 tokens per session scan B 99e67967a57d
start is a skill published in the GitHub repository orwa-mahmoud/nightshift (56 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 2,983 once invoked, about $0.0001 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-30.
Other skills, from other repositories
imap-smtp-email
Read and send email via IMAP/SMTP. Check for new/unread messages, fetch content, search mailboxes, mark as read/unread, and send emails with attachments. Works with any IMAP/SMTP server including Gmail, Outlook, 163.com, vip.163.com, 126.com, vip.126.com, 188.com, and vip.188.com.
meeting-notes
OwnPilot official general skill for converting rough meeting notes, transcripts, and call summaries into decisions, action items, owners, risks, and follow-ups. Use when the user provides meeting content or asks for notes.
template-engine
Load, validate, and populate templates consistently across frameworks.
checkpoint
Create, list, or recover mid-workflow checkpoints so interrupted work resumes from a known-good position.
update
Update AIWG through its install-aware updater and re-deploy all installed frameworks from the registry.
run
Execute a named script defined in .aiwg/aiwg.config or list all available scripts.