Borrowing it
Nothing to install: this file belongs to engasnm111/lnwjud. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/engasnm111/lnwjud/main/.agents/skills/lnwjud-scheduled-continuation/SKILL.mdgit clone --depth 1 https://github.com/engasnm111/lnwjudWrote 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/engasnm111/lnwjud/lnwjud-scheduled-continuation)<a href="https://agentmods.dev/skills/engasnm111/lnwjud/lnwjud-scheduled-continuation"><img src="https://agentmods.dev/badge/skills/engasnm111/lnwjud/lnwjud-scheduled-continuation/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/engasnm111/lnwjud/lnwjud-scheduled-continuation"><img src="https://agentmods.dev/badge/skills/engasnm111/lnwjud/lnwjud-scheduled-continuation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.02933 |
| Opus 5 | $0.00015 | $0.01466 |
| Sonnet 5 | $0.00006 | $0.00587 |
| Haiku 4.5 | $0.00003 | $0.00293 |
Grade A, and why
lnwjud-scheduled-continuation 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 yesterday.
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- jarvis-scheduled-continuation — 91% identical, 176 lines differ
- jarvis-scheduled-continuation — 91% identical, 176 lines differ
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lnwjud Scheduled Continuation
One user request owns one durable goal and at most one live Native ChatGPT watchdog. v4.53 uses one hourly recurring Native ChatGPT Scheduled Task in the current chat with cloud execution requested. The same native task ID survives ordinary wakes until the durable goal is accepted and the exact task is made non-runnable.
Non-negotiable outcome
- Never require the user to type
continue,ทำต่อ, or ask for status to resume unfinished work. - Never report completion while
get_goalisactive. run_goaldefaults toscheduledContinuation:auto; follow this skill automatically for an unfinished goal.- Use exactly one Native ChatGPT recurring Scheduled Task for a v4.53 active goal:
occurrence=interval,intervalMinutes=60, destination=current chat, cloud requested. - Never use lnwjud
scheduler, Windows Task Scheduler,schtasks.exe, cron, shell timers, browser/DOM automation, or an undocumented scheduling API as a fallback. - Native task create/update/delete/disable is host-owned. Resolve the operation from the current ChatGPT host/tool registry; never invent or hard-code an internal operation name.
- A native-host transport failure is scheduler degradation only. It never by itself completes, fails, or blocks the durable goal.
- Keep raw lease tokens, credentials, private host task IDs, and internal session IDs out of user-visible text and native task prompts.
Core model
- Normal worker lease: 600 seconds.
- Recurring cadence: 60 minutes. This cadence is independent of the worker lease.
dueAton an interval watchdog is the first scheduled firing, not a mutation handoff deadline.- If
successorDelayMinutesis omitted, a new recurring watchdog first fires in 60 minutes. - A legacy explicit
successorDelayMinutesvalue in the accepted 2–25 minute range changes only the first firing; recurrence stays hourly. - Ordinary checkpoints and ordinary recurring wakes never create a successor and never retime the recurring cadence.
- One recurring firing never consumes the native task.
outcome=consumed,reschedule_*, and per-wake successor creation are historicaloccurrence=oncecompatibility paths only. - Historical v4.52 one-time rows remain supported. Never create a recurring watchdog while a confirmed live one-time watchdog for the same goal still exists. Let the old one-time lifecycle become historical first, then create exactly one recurring watchdog.
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.
- yesterday Changed · +32 lines 676d23059690
- 5d ago Changed · +17 lines · -15 tokens per session 15a7fe3da095
- 7d ago Changed · -1 lines fde600e85e0f
- 8d ago Changed · +4 lines f76ebec53971
- 12d ago First seen · 94 lines · 45 tokens per session scan A 3cc8397be63f
lnwjud-scheduled-continuation is a skill published in the GitHub repository engasnm111/lnwjud (156 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 2,933 once invoked, about $0.0002 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
repomix-explorer
Analyze or explore a codebase (remote or local repository) by packing it with the Repomix CLI, then reading and searching the generated output. Use when the user wants a high-level understanding of an unfamiliar or large repo, not a targeted edit. Trigger for: Structure/overview: "analyze this repo", "what's the…
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
website-maintainer
Use this skill when working on the Repomix documentation website in website/ directory, including VitePress configuration, multi-language content, or translation workflows.
browser-extension-developer
Use this skill when developing or maintaining browser extension code in the browser/ directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
handoff
Transfer the current coding, debugging, planning, or architecture session to AI Badger. Use for broad session continuation; use badger-review for an independent review.
posthog
Complete guide for the PostHog plugin — REST API access for querying analytics with HogQL, managing feature flags, inspecting events and persons, reading insights, experiments, cohorts, surveys, and more.