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 agentmods add skills/jaredlangleycc/nightshift-os/challengenpx skills add jaredlangleycc/nightshift-os --skill challengegit clone --depth 1 https://github.com/jaredlangleycc/nightshift-osWrote 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/jaredlangleycc/nightshift-os/challenge)<a href="https://agentmods.dev/skills/jaredlangleycc/nightshift-os/challenge"><img src="https://agentmods.dev/badge/skills/jaredlangleycc/nightshift-os/challenge.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 | $0.00122 | $0.03130 |
| Opus 5 | $0.00061 | $0.01565 |
| Sonnet 5 | $0.00024 | $0.00626 |
| Haiku 4.5 | $0.00012 | $0.00313 |
Grade A, and why
challenge 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 4d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Challenge
The pre-mortem. Before the user locks a decision, imagine it failed and ask what killed it. Find the holes while the cost of finding them is only an awkward 20-minute conversation.
Working-parent solopreneurs cannot afford to learn from a bet that quietly failed in the background while they were at soccer practice. This skill makes the failure modes audible.
When this skill triggers
Fire when the user:
- Says "challenge me on X"
- Says "challenge this plan"
- Says "pre-mortem this"
- Says "stress-test this"
- Says "what could go wrong"
- Says "find the holes"
- Says "play devil's advocate"
- Is about to lock a decision via decision-logger that involves real money, real time, or real reputation risk
- Has presented a plan and the implicit signal is "tell me this is OK"
Do not fire when:
- The user is in
hard-callmode (different posture: hard-call holds ambiguity, challenge breaks a plan) - The user is asking for emotional support (route differently, the challenge skill is for analytical critique)
- The decision is reversible within 7 days (e.g., subscribing to a free tool)
The pre-mortem sequence
Six steps. Do not skip.
Step 1: State the plan in one sentence
Force the user to name the plan precisely. If they cannot, the plan does not exist yet.
Bad: "I'm thinking about doing some outbound." Good: "I'm going to send 50 cold emails per day to new sales managers at B2B SaaS 50-500, using the 3-angle sequence I drafted on May 18, starting Mon June 15."
The pre-mortem operates on the specific plan. Vague plans cannot be stress-tested.
Step 2: Skip 6 months. Imagine it failed.
Project the user 6 months forward. The plan ran. It failed. They are looking back.
Ask: "It's December. The plan you locked today did not work. What's the headline of the post-mortem?"
Let them name it. Then ask: "And underneath the headline, what are the 3 things that went wrong?"
The pre-mortem operates from a future-failed perspective. This is the structural move that makes the skill different from generic risk analysis.
What ships with it
2 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.
- 4d ago First seen · 246 lines · 122 tokens per session scan A dc7078d73e9d
challenge is a skill published in the GitHub repository jaredlangleycc/nightshift-os (3 stars, last pushed 1mo ago), licensed MIT. It adds 122 tokens to every session and 3,130 once invoked, about $0.0006 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
Brand Guidelines Generator
Create and maintain brand style guides for consistent visual identity.
web-vid
Turn a web app or marketing site into a recreated (not screen-recorded) Remotion promo video — pixel-faithful to the site's own design system, choreographed clicks/scrolls/zooms, rendered to MP4. Use when the user asks for a product demo video, a promo/teaser for LinkedIn or social, an "walkthrough video" of their…
demo-video-factory
Generate a custom 26s product-demo video from any SaaS URL — brand-matched scenes, a recreated product-UI "wow" scene, real screenshots, and a soundtrack. Use whenever the user wants a demo, promo, launch, or marketing video for a website or product.
pitchdocs
Generate marketing-quality repository documentation from codebase analysis. Scans 10 signal categories, extracts features with file-level evidence, and produces README, CHANGELOG, ROADMAP, and 15+ more docs. Zero runtime dependencies. For AI context file management, see ContextDocs.
brand
Brand context management for marketing sessions with continuity across conversations.
liking-factor-engineer
Analyze and engineer liking to increase rapport, persuasion, and compliance in marketing, sales, and communication contexts. Use this skill when the user wants to improve how much an audience likes them, their brand, or their message — including writing sales copy, designing onboarding flows, crafting brand voice…