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/status)<a href="https://agentmods.dev/commands/aniketkarne/claudenightswatch/status"><img src="https://agentmods.dev/badge/commands/aniketkarne/claudenightswatch/status.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.00569 |
| Opus 5 | $0.00006 | $0.00284 |
| Sonnet 5 | $0.00002 | $0.00114 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
status 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 8d 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
Nights Watch Status
Displays comprehensive status information about the Claude Nights Watch daemon, including running state, configuration, and recent activity.
Usage
/nights-watch status
Information Displayed
Daemon State
- Running/Stopped: Current daemon status
- PID: Process ID if running
- Activity Status:
- ✅ ACTIVE - Currently monitoring and executing tasks
- ⏰ WAITING - Waiting for scheduled start time
Configuration
- Task File: Location and line count of
task.md - Rules File: Location and line count of
rules.md(if present) - Start Time: Scheduled start time (if configured)
- Time Until Start: Countdown if waiting for scheduled time
Execution Info
- Recent Activity: Last 5 log entries
- Next Execution: Estimated time until next task execution
- Time Since Last Activity: Hours/minutes since last Claude usage
Status Indicators
✅ ACTIVE- Daemon is running and monitoring⏰ WAITING- Daemon is running but waiting for start time❌ STOPPED- Daemon is not running
Examples
Check daemon status:
/nights-watch status
Sample Output:
[INFO] Daemon is running with PID 12345
[INFO] Status: ✅ ACTIVE - Task execution monitoring enabled
[TASK] Task file: /path/to/task.md (42 lines)
[TASK] Rules file: /path/to/rules.md (106 lines)
[INFO] Recent activity:
[2025-10-11 14:30:00] Daemon started
[2025-10-11 14:30:05] Task file loaded
[2025-10-11 14:30:10] Monitoring began
[2025-10-11 14:35:00] Next check in 10 minutes
[2025-10-11 14:45:00] Time remaining: 234 minutes
[INFO] Estimated time until next task execution: 3h 54m
Implementation
${CLAUDE_PLUGIN_ROOT}/claude-nights-watch-manager.sh status
See Also
/nights-watch start- Start the daemon/nights-watch logs- View detailed logs/nights-watch task- View current task configuration
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.
- 8d ago First seen · 81 lines · 12 tokens per session scan A 8c2dd0ced394
status 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 569 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.