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 agentmods add skills/asheshgoplani/agent-deck/watcher-creatornpx skills add asheshgoplani/agent-deck --skill watcher-creatorgit clone --depth 1 https://github.com/asheshgoplani/agent-deckWrote 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/asheshgoplani/agent-deck/watcher-creator)<a href="https://agentmods.dev/skills/asheshgoplani/agent-deck/watcher-creator"><img src="https://agentmods.dev/badge/skills/asheshgoplani/agent-deck/watcher-creator.svg" alt="Measured on agentmods" 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 | $0.00087 | $0.02740 |
| Opus 5 | $0.00044 | $0.01370 |
| Sonnet 5 | $0.00017 | $0.00548 |
| Haiku 4.5 | $0.00009 | $0.00274 |
Grade A, and why
watcher-creator 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 5d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Watcher Creator
Overview
This skill guides users through setting up a new agent-deck watcher from scratch. A watcher listens for incoming events (webhooks, ntfy notifications, GitHub events, Slack messages, or Gmail messages) and routes them to the appropriate conductor session. The skill asks clarifying questions, collects required settings, and emits the exact CLI command and configuration files to create a working watcher.
When to use
Invoke this skill when a user says things like:
- "I want to set up a new watcher"
- "How do I connect GitHub webhooks to agent-deck?"
- "Help me route Slack messages to a conductor"
- "Create a watcher for my Gmail inbox"
- "I need agent-deck to listen for ntfy notifications"
Step-by-step conversational flow
Step 1: Choose adapter type
Ask the user which source they want to receive events from. Present the five options:
- webhook - Generic HTTP POST webhook (any service that can send HTTP)
- ntfy - ntfy.sh push notification topic
- github - GitHub repository webhooks (issues, PRs, pushes)
- slack - Slack messages via a Cloudflare Worker bridge to ntfy
- gmail - Gmail inbox via Google Cloud Pub/Sub watch
Step 2: Gather required settings for the chosen type
Once the user picks a type, ask for the settings specific to that adapter (see the per-type sections below). Ask for each required setting one at a time to avoid overwhelming the user.
Also ask:
- Watcher name: A short lowercase identifier (e.g.,
my-webhook,github-alerts). This becomes the directory name under the effective watcher data dir (${XDG_DATA_HOME:-$HOME/.local/share}/agent-deck/watcherfor new users; legacy~/.agent-deck/watcherremains in use when existing watcher state is present). - Conductor: Which conductor session this watcher should route events to by default (the
conductorfield inclients.json). - Group: Which group the conductor session lives in (the
groupfield inclients.json).
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.
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.
- 5d ago First seen · 264 lines · 87 tokens per session scan A cf82228e91bd
watcher-creator is a skill published in the GitHub repository asheshgoplani/agent-deck (831 stars, last pushed 2d ago), licensed MIT. It adds 87 tokens to every session and 2,740 once invoked, about $0.0004 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.
Other skills, from other repositories
rosetta
Reconcile ALL prior agent conversations (Claude Code, Codex, Droid/Factory, Hermes, Cursor) with git history and docs into a cited ground truth, and distill durable decision records (ADRs/PDRs/BDRs). Use whenever the user wants to catch up on or get the state of a project, build or refresh a ground truth, read or mine…
microverse
Microverse convergence loop — optimize a metric through targeted, incremental changes.
portal-gun
Cross-repo pattern extraction and transplant PRD generation.
council-of-ricks
PR branch stack review with directive generation.
meeseeks
Rotating-focus code review with commit-on-finding.
pickle-refine-prd
Refine and decompose a PRD into atomic tickets using parallel analysis.