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 skills add sammcj/agentic-coding --skill deferred-task-executiongit clone --depth 1 https://github.com/sammcj/agentic-codingWrote 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/sammcj/agentic-coding/deferred-task-execution)<a href="https://agentmods.dev/skills/sammcj/agentic-coding/deferred-task-execution"><img src="https://agentmods.dev/badge/skills/sammcj/agentic-coding/deferred-task-execution/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/sammcj/agentic-coding/deferred-task-execution"><img src="https://agentmods.dev/badge/skills/sammcj/agentic-coding/deferred-task-execution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 41 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00054 | $0.00650 |
| Opus 5.5 | $0.00022 | $0.00260 |
| Sonnet 5.5 | $0.00011 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
deferred-task-execution 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deferred Task Execution
Delays agent work until a user-specified time using a background timer script, then proceeds with the deferred task.
Script Location
~/.claude/skills/deferred-task-execution/scripts/wait-until.sh
Supported Input Formats
The script accepts one argument in either format:
Duration - relative delay from now:
30s,5m,1h,90m,2h30m,1h15m30s
Clock time - specific time of day:
14:30,9:00,3pm,3:30pm- If the time has already passed today, it waits until that time tomorrow
Workflow
Step 1: Confirm the user's intent
Confirm what task to perform and when. Parse their natural language into a wait-until argument:
| User says | Argument |
|---|---|
| "in 30 minutes" | 30m |
| "in an hour" | 1h |
| "in 2 and a half hours" | 2h30m |
| "at 3pm" | 3pm |
| "at 14:30" | 14:30 |
| "at half past 9" | 9:30am |
The script self-handles timezone via the USER_TZ variable defined at the top of wait-until.sh (defaults to Australia/Melbourne). Clock-time arguments are interpreted in that zone regardless of host TZ. Don't ask the user about timezones unless they mention travelling.
Tell the user exactly what will happen and when the timer will fire. Ask them to confirm before starting.
Step 2: Launch the timer in background
Run the wait script using Bash with run_in_background: true:
~/.claude/skills/deferred-task-execution/scripts/wait-until.sh <argument>
Note the task ID from the response -- you need it to cancel.
Step 3: Wait for the timer
Background Bash notifies you when the script exits. Wait for that notification; don't poll.
Step 4: Execute the deferred task
Once the output contains "Timer complete. Proceed with deferred task.", carry out whatever work the user requested.
Important Notes
- The agent session must remain open for the timer to work. If the user closes the session, the deferred task will not execute. Warn the user about this.
- For very long waits (multiple hours), remind the user that the session needs to stay active.
- If the user asks to cancel, use
TaskStopwith the background task ID. - Always tell the user the calculated wake time so they know when to expect the action.
What ships with it
1 file 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.
- 11d ago Changed · -6 lines · -1 tokens per session b81dda4a9c85
- 1mo ago First seen · 75 lines · 55 tokens per session scan A b163cd9072a7
deferred-task-execution is a skill published in the GitHub repository sammcj/agentic-coding (164 stars, last pushed 3d ago), licensed Apache-2.0. It adds 54 tokens to every session and 650 once invoked, about $0.0002 per session on Opus 5.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
pb-supervise-parallel-mission
Run N parallel worker agents on disjoint file/topic ownership and fan their results into one verified deliverable. Trigger when supervising - 'I am the supervisor', 'spawn parallel workers', 'fan-in several agents', 'decompose this mission and delegate'.
pb-new-agent-session
Spawn one worker agent on the agentproto daemon, drive it with a brief and follow-ups to a verified result, then tear it down cleanly. Trigger when delegating a single task - 'spawn an agent', 'delegate this to a worker', 'run an agent to completion', 'drive an agent session'.
ap-cron
Schedule recurring or one-shot jobs on the agentproto daemon — croncreate with command, agent, or prompt-session actions, cronlist to inspect, cronrun to test-fire, crondelete to remove. Trigger when asked for cron jobs, scheduled agent runs, nightly check-ins, one-shot timers, or durable session re-pings.
ap-terminal
Open a real PTY terminal session through agentproto to drive interactive TUIs (vim, htop, an interactive CLI wizard, a nested claude TUI) with live keystrokes and byte-buffered output. Trigger phrases include "open a terminal", "start a PTY session", "type into the interactive prompt", "attach a terminal panel", "send…
ap-wait-durable
Get notified when a spawned agentproto session finishes WITHOUT blocking your own turn — background a CLI wait with a completion notification, or arm a cron re-ping as a durable fallback that survives daemon restarts. Triggers — "notify me when it's done", "wait in the background", "don't block on this", "durable…
pb-boss-checkins
Stay accountable on a long mission by scheduling a cron boss that re-prompts your own session on a fixed local-time schedule. Trigger for durable check-ins - 'cron a status report', 'wake me on a schedule', 're-prompt my session periodically', 'mission check-in boss'.