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 iamcxa/kc-claude-plugins --skill kc-nightwatch-reportgit clone --depth 1 https://github.com/iamcxa/kc-claude-pluginsWrote 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-report)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/kc-nightwatch-report"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/kc-nightwatch-report/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-report"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/kc-nightwatch-report.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.00058 | $0.02684 |
| Opus 5 | $0.00029 | $0.01342 |
| Sonnet 5 | $0.00012 | $0.00537 |
| Haiku 4.5 | $0.00006 | $0.00268 |
Grade A, and why
kc-nightwatch-report 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 10d 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 — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kc-nightwatch Report
View nightwatch results or review pending proposals.
Arguments
/kc-nightwatch-report— status mode (default): show last run summary, recent activity, trends/kc-nightwatch-report --last— trace mode: show detailed execution trace of last run/kc-nightwatch-report --compare— compare mode: compare last N runs side-by-side/kc-nightwatch-report --review— review mode: interactive review of pending proposal and fix branches
Route to the appropriate section below.
Status Mode (default)
Step 1: Read Improvement Log
Read ~/.claude/kc-plugins-config/nightwatch-improvement-log.md from the kc-nightwatch plugin directory.
The file has YAML frontmatter with last_run and runs fields, followed by markdown sections organized by date.
If No Runs Yet
If last_run: null or runs: 0:
🌙 kc-nightwatch — 尚未執行
No nightly runs recorded yet.
Run `/kc-nightwatch` manually or wait for the next cron cycle.
Stop here.
Step 2: Present Summary
Display:
🌙 kc-nightwatch Report
Last run: {last_run}
Total runs: {runs}
Step 3: Recent Improvements (Last 7 Days)
Parse the improvement-log.md sections for entries within the last 7 days.
Group by action type:
## Recent Activity (last 7 days)
🔧 Auto-fixes:
• {date} — {plugin}: {summary}
Branch: {branch} | PR: {pr_link or "local branch"}
📋 Proposals:
• {date} — {plugin}: {summary}
Branch: {branch} | PR: {pr_link or "local branch"}
⏭️ Skipped:
• {date} — {plugin}: {signal_id} — {reason}
PR Link Display
For entries with PR links (remote repos):
- Show clickable link:
[PR #{number}]({url})
For entries with local branches only (no remote):
- Show branch name:
local branch: {branch_name} - Include a note:
(review with: git log main..{branch_name})
If No Recent Activity
If no entries within last 7 days:
No activity in the last 7 days. All quiet. 🌙
Step 4: Signal Trends (Optional)
If there are 3+ runs in the log, look for patterns:
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.
- 10d ago First seen · 346 lines · 58 tokens per session scan A f8081ffbfb86
kc-nightwatch-report is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 2,684 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…