What is remote-watch?

A status checker for remote code reviews and continuous-integration systems, such as GitHub pull requests, Gerrit, or Jenkins. It reports whether a submission is merged, still waiting, rejected, or unknown.

Use it to check pull requests, code reviews, build jobs, or custom web endpoints. Only use configuration files you trust, because they can run commands with full computer access.

It avoids repeatedly checking different review or build systems by hand. It can reuse saved workspace settings or details provided for the current check.

remote-watch — Skill for Claude Code and Codex by cintia09/CodeNook

Install

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.

Any agent

npx skills add cintia09/CodeNook --skill remote-watch

Clone the repo

git clone --depth 1 https://github.com/cintia09/CodeNook

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cintia09/codenook/remote-watch/github.svg)](https://agentmods.dev/skills/cintia09/codenook/remote-watch)

Your own site

<a href="https://agentmods.dev/skills/cintia09/codenook/remote-watch"><img src="https://agentmods.dev/badge/skills/cintia09/codenook/remote-watch/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cintia09/codenook/remote-watch"><img src="https://agentmods.dev/badge/skills/cintia09/codenook/remote-watch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,139 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00002	$0.01139
Opus 5.5	$0.00001	$0.00456
Sonnet 5.5	$0.00000	$0.00228
Haiku 4.5	$0.00000	$0.00114

Measured 2mo ago against content hash 507de93eb79c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

remote-watch 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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (watch.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

`subprocess.run(..., shell=True)`. The Python execution gives the

plugins/development/skills/remote-watch/SKILL.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

remote-watch — plugin-shipped skill (development plugin)

Role

Probe a remote review / CI endpoint for the status of a submission and return one of merged, pending, rejected, or unknown. The skill itself knows nothing about Gerrit / GitHub / Jenkins / etc. — specifics live in workspace memory or are supplied per-call.

Security / threat model

--config <path> is executed as a Python module (via runpy.run_path); the module-level PROBE_CMD is then executed via subprocess.run(..., shell=True). The Python execution gives the config full host privileges (it can import os; os.system(...) etc.) before any probe even starts. This is intentional — the memory-first pattern needs full flexibility to wrap arbitrary review backends (custom CLIs, multi-step queries, env-var preludes). Consequences:

The caller is responsible for trust. Only point --config at: (a) a workspace-memory entry under .codenook/memory/knowledge/ that a human author wrote / reviewed; OR (b) a snippet just pasted by the current user via HITL.
Never load a --config file fetched over the network without human review first.
The skill makes no attempt to sandbox the config or the probe — anything Python (and shell=True) can do, the config can do.
Memory entries shipped by plugins (under .codenook/plugins/<id>/) are not auto-trusted; they reach --config only after a human promotes the embedded snippet to a memory file.

Three-tier resolution (memory-first → user-ask)

Tier 1 — cheap probe. If the target dir contains a .github/ folder and gh is on PATH, run gh pr view <ref> --json state. If it contains a .gerrit/ marker and ssh to the host succeeds, run the recorded ssh gerrit query command. These two probes ship as defaults so the most common cases just work.
Tier 2 — --config <path>. The caller (submitter role) does:
```
<codenook> knowledge search "remote-watch-config target=<basename>"
```
If a memory hit is found, the entry contains a Python snippet that defines (as module-level variables):
- PROBE_CMD: str — command line to run; stdout becomes status text
- STATUS_REGEX_MERGED: str — regex matched against stdout
- STATUS_REGEX_REJECTED: str — regex matched against stdout
- STATUS_REGEX_PENDING: str — regex matched against stdout (default ".*")

Read the full file on GitHub · 114 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

watch.py 6.7 KB runs code

Changes

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.

2mo ago First seen · 114 lines · 2 tokens per session scan A 507de93eb79c

Subscribe to this mod's changes

remote-watch is a skill published in the GitHub repository cintia09/CodeNook (5 stars, last pushed 1mo ago), licensed MIT. It adds 2 tokens to every session and 1,139 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

CI and CD Code review DevOps and cloud development plugin-shipped remote-watch skill submit

remote-watch next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
remote-watchcintia09/CodeNook	Skill	5	1mo ago	MIT	A	2	Claude Code, Codex
green-prsdiegosouzapw/OmniRoute	Skill	85k	yesterday	MIT	A	51	Claude Code, Codex
clawhub-pr-maintaineropenclaw/clawhub	Skill	9.6k	yesterday	MIT	A	50	Claude Code, Codex
autoreviewopenclaw/clawhub	Skill	9.6k	yesterday	MIT	A	17	Claude Code, Codex
mindosGeminiLight/MindOS	Skill	705	today	MIT	A	136	Claude Code
tech-lead/code-reviewechoVic/boss-skill	Skill	546	yesterday	MIT	A	52	Claude Code
code-quality-principlesathola/claude-night-market	Skill	348	yesterday	MIT	A	38	Claude Code

remote-watch