Borrowing it
Nothing to install: this file belongs to skyliner2008/JARVIS-MCP. 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/skyliner2008/JARVIS-MCP/main/.agents/skills/jarvis-scheduled-continuation/SKILL.mdgit clone --depth 1 https://github.com/skyliner2008/JARVIS-MCPWrote 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/skyliner2008/jarvis-mcp/jarvis-scheduled-continuation)<a href="https://agentmods.dev/skills/skyliner2008/jarvis-mcp/jarvis-scheduled-continuation"><img src="https://agentmods.dev/badge/skills/skyliner2008/jarvis-mcp/jarvis-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/skyliner2008/jarvis-mcp/jarvis-scheduled-continuation"><img src="https://agentmods.dev/badge/skills/skyliner2008/jarvis-mcp/jarvis-scheduled-continuation.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.00043 | $0.02452 |
| Opus 5 | $0.00022 | $0.01226 |
| Sonnet 5 | $0.00009 | $0.00490 |
| Haiku 4.5 | $0.00004 | $0.00245 |
Grade A, and why
jarvis-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 11d 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.
This is a copy
91% identical to lnwjud-scheduled-continuation — 176 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jarvis Scheduled Continuation
One user request starts one durable chain: acquire the goal, arm one cloud successor, keep doing useful work, hand off when necessary, and stop only after the goal is verifiably terminal.
Non-negotiable outcome
- Never require the user to type “continue”, “ทำต่อ”, or ask for status to restart an unfinished goal.
- Never send a completion report while
get_goalreportsactive. - A request to stop scheduling cancels only the successor. It does not cancel, block, pause, or complete the durable goal. Continue in the current run and still call
finish_goalwhen the work is actually done. cancel_goalandcancel_scheduled_continuationare independent controls: the former records the goal as cancelled, aborts in-flight fenced MCP requests, and stops every tracked process, Codex task, and shell task; the latter cancels only the waiting successor. Call both when the user wants both effects.- Use one native one-time cloud ChatGPT Scheduled Task in the current chat. Never use recurrence, Windows Task Scheduler,
schtasks.exe, cron, shell timers, browser automation, or undocumented scheduling APIs. - Native task creation, update, and deletion are host-owned. jarvis stores the reservation, receipts, claim, and cancellation truth.
Start or resume
run_goal defaults to scheduledContinuation: auto. When its result contains continuationDirective.mode: auto, the client MUST apply this skill automatically even when the user did not name $jarvis-scheduled-continuation. The directive is the durable-goal opt-in signal: never require another user prompt to resume an unfinished goal. Use scheduledContinuation: off only when the user explicitly disables future scheduling; that disables the successor, not the current goal work.
- Call
run_goalwith a stable workspace and goal key using the normal 600-second (10-minute) lease. Never override this workflow to an hour-long lease. Keep the returned lease token and generation private. The lease is a short crash-recovery window, not the expected work duration; real checkpoint/fenced-mutation activity renews it while work is actually alive. - Read the durable checkpoint and do the next useful work. Record real milestones with
checkpoint_goal; do not checkpoint merely because time elapsed. - After the first checkpoint, call
prepare_scheduled_continuationand create exactly one native one-time task from itsscheduleRequest. Recordcreatedwith the real native task ID andrunsOn: cloudimmediately before relying on it. Never yield after native creation while durable state is still onlyprepared. - Choose
successorDelayMinutesadaptively within 2–25 minutes. The API default is deliberately 2 minutes as a fail-safe: any longer watchdog must be explicit.
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.
- 11d ago First seen · 94 lines · 43 tokens per session scan A dd5dcd4e847e
jarvis-scheduled-continuation is a skill published in the GitHub repository skyliner2008/JARVIS-MCP (0 stars, last pushed 13d ago), licensed MIT. It adds 43 tokens to every session and 2,452 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to lnwjud-scheduled-continuation, differing in 176 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…