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/lftpadilla/agent-dev-kit/overnight-tasknpx skills add LFTPadilla/agent-dev-kit --skill overnight-taskgit clone --depth 1 https://github.com/LFTPadilla/agent-dev-kitWhat 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.00065 | $0.00718 |
| Opus 5 | $0.00032 | $0.00359 |
| Sonnet 5 | $0.00013 | $0.00144 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
overnight-task 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 2d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
overnight-task
Use this skill when the user explicitly says they are leaving a task running for hours, overnight, or unattended and asks the agent not to stop for clarifying questions.
Invocation Signals
- "tienes toda la noche"
- "no me hagas más preguntas"
- "no voy a estar disponible"
- "deja esto funcionando"
- "apenas termines puedes apagar..."
- "necesito un reporte completo para mañana"
- "audita todo lo que encuentres"
Do not invoke for short, interactive, or low-risk tasks where the user is present.
Operating Contract
- No questions after activation. Make conservative decisions and document them.
- Plan before execution.
- Keep a journal of material actions and decisions.
- Checkpoint every 2-3 tasks or before risk increases.
- Verify each completed task.
- Do not commit, push, deploy, mutate production, touch secrets, or shut down machines unless the user explicitly authorizes that action in the same session.
- Produce a final report with what changed, what was verified, what remains open, and what the next session should review.
Recommended Runner
Initialize the run directory:
node overnight-task-kit/scripts/overnight-runner.mjs init --title "<short-title>"
Then use the generated files:
SPEC.md: falsifiable scope and ambiguity assessment.PLAN.md: vertical slices with acceptance criteria and verification commands.JOURNAL.md: chronological record.CHECKPOINTS.md: stop/continue gates.REPORT.md: final handoff.
Mandatory Flow
- Research: inspect local docs, code, backlog, and relevant external docs if the task depends on current APIs or packages.
- SPEC: write requirements, non-goals, risks, assumptions, and ambiguity score.
- PLAN: split into small independently verifiable tasks.
- Execute: complete one task at a time; update plan status as work lands.
- Verify: run tests, linters, smoke checks, or manual checks appropriate to the task.
- Report: fill
REPORT.mdand include plan deviations. - Shutdown handoff: if shutdown was authorized, follow the private overlay's shutdown procedure. If none exists, stop and report that shutdown was skipped.
What ships with it
10 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.
- overnight-task.opencode.md 5.7 KB
- references/agent-quickref.md 4.1 KB
- references/connections.md 510 B
- references/learnings-template.md 694 B
- references/plan-template.md 287 B
- references/planning-and-task-breakdown-canonical.md 6.8 KB
- references/planning-protocol.md 1019 B
- references/session-learnings-template.md 239 B
- references/shutdown-sequence.md 590 B
- references/spec-template.md 473 B
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.
- 2d ago First seen · 93 lines · 65 tokens per session scan A 5b977d88c50f
overnight-task is a skill published in the GitHub repository LFTPadilla/agent-dev-kit (2 stars, last pushed 4d ago), licensed MIT. It adds 65 tokens to every session and 718 once invoked, about $0.0003 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
deep-research
Enterprise-grade deep research with multi-phase pipeline - autonomous web research, source credibility scoring, cross-referencing, synthesis, and validated reports for market analysis, competitive intel, and technical investigations.
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…
build-monetized-app
Use when the task is building a new app on Eliza Cloud that earns money — chat apps, agent apps, MCP-backed tools, anything that calls the cloud's chat/messages/inference endpoints on behalf of users. Covers app registration, container deploy, markup configuration, affiliate header, app charge requests, x402 payment…
contribute-to-eliza
Finish and prove a scoped elizaOS GitHub issue, or independently review and repair an open elizaOS pull request. Use when contributing compute to elizaOS by selecting unclaimed work, implementing or reviewing changes, adding real tests and evidence, validating artifacts, or preparing a contribution for maintainer…
eliza-cloud
Use when the task involves Eliza Cloud or elizaOS Cloud as a managed backend, app platform, deployment target, billing layer, or monetization surface. The catch-all skill for any user request about THEIR existing apps / containers / earnings / credits / api-keys / analytics / billing / payment requests / payouts …
discord
Use when you need to control Discord from Otto via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, create/edit/delete channels and categories, fetch permissions or member/role/channel info, set bot presence/activity, or handle moderation actions in…