agent-fleet: Skill for Claude Code

.pi/agent-fleet/hermes/skills/hub-watchdog/SKILL.md

hub-watchdog is a skill for Claude Code, Codex from chankov/agent-fleet. It costs 32 tokens per session (1,524 once invoked), scanned A, original, MIT.

A local watchdog for observing an authenticated Agent Hub profile from the foreground. It checks status or configuration and can watch activity until you stop it.

In plain words
What is it for?
Use it to validate an observation setup, check the resolved autonomy and delivery settings, or monitor one Hub profile while preventing duplicate watchers.
Why use it?
It helps operators inspect a Hub without accidentally starting background processes, reopening sessions, or using an unintended fallback route.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is chankov/agent-fleet's own configuration. It tells Claude Code and Codex how to work on agent-fleet itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agent-fleet configures →

Reuse

Borrowing it

Nothing to install: this file belongs to chankov/agent-fleet. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/chankov/agent-fleet/main/.pi/agent-fleet/hermes/skills/hub-watchdog/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/chankov/agent-fleet

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.

agentmods badge for hub-watchdog

README.md
[![agentmods](https://agentmods.dev/badge/skills/chankov/agent-fleet/hub-watchdog/github.svg)](https://agentmods.dev/skills/chankov/agent-fleet/hub-watchdog)
Your own site
<a href="https://agentmods.dev/skills/chankov/agent-fleet/hub-watchdog"><img src="https://agentmods.dev/badge/skills/chankov/agent-fleet/hub-watchdog/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 hub-watchdog

Your own site · 80×15
<a href="https://agentmods.dev/skills/chankov/agent-fleet/hub-watchdog"><img src="https://agentmods.dev/badge/skills/chankov/agent-fleet/hub-watchdog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,524 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Data Exfiltration · line 31
    Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.
    Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
  • medium Tool Misuse · line 21
    Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.
    Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
How audits are shown
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.00032 $0.01524
Opus 5.5 $0.00013 $0.00610
Sonnet 5.5 $0.00006 $0.00305
Haiku 4.5 $0.00003 $0.00152

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

Security

Grade A, and why

hub-watchdog 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 1mo ago.

The scan reads SKILL.md. This mod also ships 9 executable files (scripts/watchdog_actions.py, scripts/watchdog_contract.py, scripts/watchdog_delivery.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.

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.

.pi/agent-fleet/hermes/skills/hub-watchdog/SKILL.md · 77 lines

How it starts

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

Hub Watchdog

hub-watchdog is a packaged source skill, not a service or an enabled Hermes integration. Run it only as an explicit foreground operator action:

python3 .pi/agent-fleet/scripts/watchdog.py status --invocation-json '<json>'
python3 .pi/agent-fleet/scripts/watchdog.py validate-config --invocation-json '<json>'
python3 .pi/agent-fleet/scripts/watchdog.py watch --invocation-json '<json>'

status and validate-config report the resolved autonomy tier and delivery disposition without connecting to anything. Run them before watch and stop if either reports something you did not intend.

Default and maximum autonomy are observe. Send SIGINT to stop the foreground process; it releases its per-profile watch.lock, closes its socket clients and any long-poll waiter, and leaves the local journal in place. Do not create a daemon, schedule it, wake/reopen a Hermes session, or use a last-chat/default-route fallback. A second watcher for the same profile fails closed with watcher_locked rather than sharing state.

Discovery is profile-scoped

Read exactly one discovery record from the namespace the invocation names — the validated profile key and hub key under the configured runtime directory. Never scan a runtime root, walk sibling profiles, or fall back to another namespace when a lease is expired, a token is missing, or a socket is gone. An unsafe runtime mode, a symlink, a world-readable token, an expired lease, or more than one discovery entry is a refusal.

Identity is bound on every request: the configured profile key, hub instance, and owner must all equal what live discovery reports. A mismatch is a refusal, not a fallback. After an owner rollover, rediscover from scratch; never reuse the previous owner's token or socket, and never re-drive a request that was already accepted.

Gate O: currently closed

There is no checked-in genuine live proof of a Hermes originating-chat identity, incremental-update, wake/reconnect, or session API. hermes send --to is an explicit destination only; it is not origin evidence. A validator, fixture, fake adapter, or local UDS test cannot close Gate O.

Read the full file on GitHub · 77 lines

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. 1mo ago Changed cfbc842d12ab
  2. 2mo ago First seen · 77 lines · 32 tokens per session scan A 085e4a3798b3

Subscribe to this mod's changes

hub-watchdog is a skill published in the GitHub repository chankov/agent-fleet (20 stars, last pushed 12d ago), licensed MIT. It adds 32 tokens to every session and 1,524 once invoked, about $0.0001 per session on Opus 5.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-09-03.

Related

hub-watchdog compared with skills from other repositories

hub-watchdog next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
hub-watchdogchankov/agent-fleetSkill2012d agoMITA32Claude Code, Codex
systematic-debuggingopen-metadata/OpenMetadataSkill16kyesterdayApache-2.0A37Claude Code
log-error-digestzebbern/claude-code-guideSkill4.7k3d agoMITA71Claude Code, Codex
cwv-optimizeradobe/skillsSkill319yesterdayApache-2.0A112Claude Code
ci-fixersipyourdrink-ltd/bernsteinSkill1.2kyesterdayApache-2.0A15Claude Code, Codex
triaging-web-analytics-supportPostHog/posthogSkill41kyesterdaynoneA151Claude Code, Codex
diagnosing-missing-recordingsPostHog/posthogSkill41kyesterdaynoneA76Claude Code, Codex