Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add aniketkarne/ClaudeNightsWatch/plugin install ClaudeNightsWatchWrote 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/commands/aniketkarne/claudenightswatch/start)<a href="https://agentmods.dev/commands/aniketkarne/claudenightswatch/start"><img src="https://agentmods.dev/badge/commands/aniketkarne/claudenightswatch/start.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.1 | $0.00012 | $0.00499 |
| Opus 5 | $0.00006 | $0.00249 |
| Sonnet 5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
start 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 7d 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.
What it actually says
Start Nights Watch Daemon
Starts the Claude Nights Watch daemon to monitor your Claude usage windows and execute tasks from task.md automatically.
Usage
/nights-watch start [OPTIONS]
Options
--at TIME- Schedule daemon to start monitoring at a specific time- Format:
HH:MM(today) orYYYY-MM-DD HH:MM(specific date/time) - Daemon will wait until scheduled time before beginning task execution
- Format:
What It Does
- Checks for required files (
task.mdin current directory) - Starts background daemon process
- Begins monitoring Claude usage windows
- Executes tasks when approaching the 5-hour limit
- Logs all activity to
logs/claude-nights-watch-daemon.log
Prerequisites
task.mdfile must exist in current directory (create one if not present)rules.mdfile is recommended for safety constraints (optional)- Claude CLI must be installed and configured
Examples
Start immediately:
/nights-watch start
Start at 9 AM today:
/nights-watch start --at "09:00"
Start at specific date and time:
/nights-watch start --at "2025-10-12 14:30"
Implementation
${CLAUDE_PLUGIN_ROOT}/claude-nights-watch-manager.sh start "$@"
Safety Notice
⚠️ The daemon uses --dangerously-skip-permissions for autonomous execution. Always:
- Test tasks manually first
- Use comprehensive
rules.mdfor safety constraints - Monitor logs regularly
- Start with simple, non-destructive tasks
See Also
/nights-watch stop- Stop the daemon/nights-watch status- Check daemon status/nights-watch task- View/edit current task/nights-watch logs- View execution logs
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.
- 7d ago First seen · 78 lines · 12 tokens per session scan A d96b77aede82
start is a command published in the GitHub repository aniketkarne/ClaudeNightsWatch (370 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 499 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.