Agent Deck is a terminal session manager that lets developers monitor and switch between multiple AI coding-agent sessions from one text interface. It helps people organize agents working across projects with groups, search, forking, Git worktrees, cost tracking, and a phone-controlled conductor. The catalogue entries extend its use with skills, commands, and a plugin.
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 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/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/asheshgoplani/agent-deck/watcher-creator"><img src="https://agentmods.dev/badge/skills/asheshgoplani/agent-deck/watcher-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 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 Privilege Escalation · line 168 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 177 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 10 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00087 | $0.03276 |
| Opus 5.5 | $0.00035 | $0.01310 |
| Sonnet 5.5 | $0.00017 | $0.00655 |
| Haiku 4.5 | $0.00009 | $0.00328 |
Grade B, and why
watcher-creator scanned grade B with 2 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 today.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
**Secret:** `secret` (string) in `[source]`. `watcher create webhook` generates one and stores it in `watcher.toml` (chmod 600), or takes it from `$WEBHOOK_SECRET` or `--secret-file <path>` (chmod 600). Never put it on t Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
import hashlib, hmac, re, time, urllib.request How it starts
The opening of the file, as written. The whole thing — 280 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.
- today Changed · +16 lines scan A → B 05d3afc24c74
- 1mo 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 (1,157 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 3,276 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agnix
Use when user asks to 'lint agent configs', 'validate skills', 'check CLAUDE.md', 'validate hooks', 'lint MCP'. Validates agent configuration files against 702 rules across 10+ AI tools.
fast-resume
Search local coding-agent session history and identify safe resume commands. Use when the user asks to find, inspect, continue, or recover previous work from Claude Code, Codex, Pi, or another agent indexed by fast-resume.
agent-team-protocol
Multi-agent delegation rules, three-phase workflow (Plan/Build/Review), model selection, collaboration gates, and Ralph Loop integration.
opus-4-7-features
Optional guidance for sessions using Claude Opus 4.7: adaptive thinking, xhigh effort, prompt caching, /btw side questions.
phase-workflow
Phase transition rules, post-phase verification steps, peer review validation, and commit-gate approval flow.
copilot-conventions
Cross-copilot portable conventions: target alignment, complexity control, minimal changes, git discipline, and project structure.