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 iamcxa/kc-claude-plugins/plugin install kc-nightwatchWrote 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/iamcxa/kc-claude-plugins/kc-nightwatch-config)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/kc-nightwatch-config"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/kc-nightwatch-config/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/iamcxa/kc-claude-plugins/kc-nightwatch-config"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/kc-nightwatch-config.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.00054 | $0.02450 |
| Opus 5 | $0.00027 | $0.01225 |
| Sonnet 5 | $0.00011 | $0.00490 |
| Haiku 4.5 | $0.00005 | $0.00245 |
Grade A, and why
kc-nightwatch-config 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 12d 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kc-nightwatch Config
Manage nightwatch schedule, Slack channel, and monitored plugins.
Arguments
/kc-nightwatch-config— overview: show current config status/kc-nightwatch-config schedule— manage cron schedule/kc-nightwatch-config channel— configure Slack notification channel/kc-nightwatch-config plugins— view and manage monitored plugins
Route to the appropriate section below.
Bootstrap (auto, runs before any mode)
Check if config directory and files exist. If not, create them:
mkdir -p ~/.claude/kc-plugins-config
If nightwatch-targets.yaml does not exist:
Create a starter file with one commented-out example:
# kc-nightwatch monitoring targets
# See README.md for field documentation
#
# Example:
# my-plugin:
# type: plugin
# path: ~/Project/my-workspace/my-plugin
# repo: my-plugins
# north_star: "My plugin works perfectly"
# keywords: [my-plugin, feature-x]
# sources: [journal, episodic-memory, memory-md]
# actions: [quick-fix, proposal]
# proxy_signals:
# - id: quality
# description: "Plugin quality metric"
# target: "100%"
targets: {}
Log: [BOOTSTRAP] Created nightwatch-targets.yaml — add targets with /kc-nightwatch-config plugins
If nightwatch-improvement-log.md does not exist:
Create with initial frontmatter:
---
last_run: null
runs: 0
---
If channels.yaml does not exist: Create empty file. Channel will be asked on first run.
If language.yaml does not exist: Create with default:
default: en
overrides: []
Overview (no args)
Show current configuration at a glance:
Step 1: Gather Status
# launchd status
launchctl list 2>/dev/null | grep com.kc.nightwatch
# Installed plist
ls -la ~/Library/LaunchAgents/com.kc.nightwatch.plist 2>/dev/null
# Wrapper script
ls -la ~/.claude/scripts/nightwatch-cron.sh 2>/dev/null
Read:
~/.claude/kc-plugins-config/channels.yaml→nightwatchkey~/.claude/kc-plugins-config/nightwatch-targets.yaml→ target count + types~/.claude/kc-plugins-config/nightwatch-improvement-log.md(from kc-nightwatch plugin dir) → last run + total runs
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.
- 12d ago First seen · 333 lines · 54 tokens per session scan A dc3ccc16bcc0
kc-nightwatch-config is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 2,450 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
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…