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-nightwatchgit 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)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/kc-nightwatch"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/kc-nightwatch/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"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/kc-nightwatch.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.00038 | $0.13159 |
| Opus 5 | $0.00019 | $0.06580 |
| Sonnet 5 | $0.00008 | $0.02632 |
| Haiku 4.5 | $0.00004 | $0.01316 |
Grade A, and why
kc-nightwatch scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "$WEBHOOK_URL" \ How it starts
The opening of the file, as written. The whole thing — 1,229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kc-nightwatch — Nightly Plugin Improvement
Autonomous nightly pipeline that patrols each plugin, fixes structural issues, and proposes north-star-aligned improvements.
Core philosophy: Find cracks in the wall and patch them nightly. Never tear down a wall.
Arguments
Parse the invocation arguments:
/kc-nightwatch— production mode (all safety guards active)/kc-nightwatch --self-repair— self-repair mode: validate config, collect feedback, check own forge status. Runs as Phase SR (before Phase 0). Does NOT run the regular pipeline./kc-nightwatch --dry-run— dry-run mode: bypassesskip_if_dirtyandskip_if_recent_human_commitguards. Combinable with any mode.
When --dry-run is active, prefix all log output with [DRY-RUN].
When --self-repair is active, prefix all log output with [SELF-REPAIR].
Mode routing:
--self-repair→ execute Phase SR only, then stop- no args /
--dry-runonly → execute Phase 0-5 (existing pipeline)
Prerequisites Check
Before starting, check for optional plugin dependencies:
- kc-plugin-forge — invoke
Skill: "kc-plugin-forge"withvalidate-only(used in Phase 1)
If kc-plugin-forge is not loaded:
[WARN] kc-plugin-forge not loaded — Phase 1 (forge validation) will be skipped
Set forge_available = false and continue. Phase 1 will be skipped entirely.
Phase SR: Self-Repair (--self-repair mode only)
Runs in a dedicated session before the regular pipeline. Three responsibilities:
- Config validation + auto-fix
- Feedback collection from previous runs
- Own plugin forge check
Step SR.1: Load Self-Repair Config
Read:
~/.claude/kc-plugins-config/nightwatch-targets.yaml— targets to validateconfig/safety.yaml→self_repairsection — limits and matching algorithm~/.claude/kc-plugins-config/nightwatch-improvement-log.md→last_runtimestamp (for feedback scan window)
Step SR.2: Config Validation + Auto-Fix
For each target in nightwatch-targets.yaml:
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.
- 9d ago First seen · 1,229 lines · 38 tokens per session scan A 6405e8ed4329
kc-nightwatch is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 13,159 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…