connector-watcher-template

connector-watcher-template is an agent for Claude Code from jianzhichun/emerge. It costs 28 tokens per session (158 once invoked), scanned A, original, MIT.

A template for watcher agents that monitor configured local activity for a specific connector. It keeps connector-specific rules in configuration files.

In plain words
What is it for?
Use it to create watcher agents that read approved local sources, spot repeated behavior, remove sensitive details, and send suggestions to a runner.
Why use it?
It prevents each connector watcher from needing its own hard-coded product logic. It also keeps watchers limited to observing and suggesting rather than changing system state.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the emerge plugin — 15 skills, 10 commands, 3 agents, 24 hooks shipped together

Good fit Use it to create watcher agents that read approved local sources, spot repeated behavior, remove sensitive details, and send suggestions to a runner.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/jianzhichun/emerge/connector-watcher-template
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.

Clone the repo
git clone --depth 1 https://github.com/jianzhichun/emerge

Made for: Claude Code.

Or install emerge, the plugin that ships this one along with the rest of its 15 skills, 10 commands, 3 agents, 24 hooks.

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.

agentmods badge for connector-watcher-template

README.md
[![agentmods](https://agentmods.dev/badge/agents/jianzhichun/emerge/connector-watcher-template/github.svg)](https://agentmods.dev/agents/jianzhichun/emerge/connector-watcher-template)
Your own site
<a href="https://agentmods.dev/agents/jianzhichun/emerge/connector-watcher-template"><img src="https://agentmods.dev/badge/agents/jianzhichun/emerge/connector-watcher-template/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.

agentmods 80×15 button for connector-watcher-template

Your own site · 80×15
<a href="https://agentmods.dev/agents/jianzhichun/emerge/connector-watcher-template"><img src="https://agentmods.dev/badge/agents/jianzhichun/emerge/connector-watcher-template.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 158 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00158
Opus 5 $0.00014 $0.00079
Sonnet 5 $0.00006 $0.00032
Haiku 4.5 $0.00003 $0.00016

Measured 9d ago against content hash 081e0f3d0296, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

connector-watcher-template 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 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.

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.

agents/connector-watcher-template.md · 22 lines

What it actually says

You are a runner-side watcher for the connector described by the active watcher_profile.yaml.

Load connector-specific behavior from configuration, not from this product asset:

  • connector
  • allowed local sources
  • redaction rules
  • candidate intent hints
  • preference fields and decay windows

Observe only configured local sources. Emit redacted runner_subagent_message suggestions when repeated behavior appears.

You must not create pipelines, call execution or crystallization tools, update policy, push Memory Hub data, or turn local observations into deployable 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.

  1. 9d ago First seen · 22 lines · 28 tokens per session scan A 081e0f3d0296

Subscribe to this mod's changes

connector-watcher-template is an agent published in the GitHub repository jianzhichun/emerge (107 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 158 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.