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 SethGammon/Citadel --skill watchgit clone --depth 1 https://github.com/SethGammon/CitadelWrote 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/sethgammon/citadel/watch)<a href="https://agentmods.dev/skills/sethgammon/citadel/watch"><img src="https://agentmods.dev/badge/skills/sethgammon/citadel/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.
<a href="https://agentmods.dev/skills/sethgammon/citadel/watch"><img src="https://agentmods.dev/badge/skills/sethgammon/citadel/watch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00070 | $0.02992 |
| Opus 5.5 | $0.00028 | $0.01197 |
| Sonnet 5.5 | $0.00014 | $0.00598 |
| Haiku 4.5 | $0.00007 | $0.00299 |
Grade A, and why
watch 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.
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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/watch -- File Sentinel
Use when the user wants automatic reactions to file changes or marker comments (@citadel:).
Do NOT use for one-off file inspection or tasks that need human judgment per file.
Orientation
Use when: running a file sentinel that triggers a skill or command automatically when watched paths change. Don't use when: monitoring CI status on a PR (use /pr-watch); running a one-shot verification check (use /verify).
Default execution path (READ FIRST)
/watch start does NOT call CronCreate by default. Only pass --remote
to use Anthropic's routine system, and only after explicit user confirmation.
CronCreate counts against the 15 routine runs / 24h cap — at the default
5-minute interval a watch exhausts the quota in under an hour.
Default flow — /watch start (no --remote flag)
- Do Steps 1 and 2 below (check existing watch, determine baseline commit).
- Skip Step 3 — do NOT call
CronCreate. LeavecronId: nullin state. - Write the state file (Step 4) with
status: "watching". - Output:
Watch state created: .planning/watch-state.json Baseline: {commit hash, first 7 chars} To start real-time watching, run in a separate terminal: npm run watch:local For cloud-persistent polling (machine off, user away): /watch start --remote (uses CronCreate, counts against 15/day cap)
Opt-in routine flow — /watch start --remote
Only when --remote is explicitly passed:
- Confirm: "This will use
CronCreate, which counts against your 15 routine runs / 24h quota. At a 5-minute interval this exhausts the quota in under an hour. Continue? (y/N)" - On confirmation, run the full Step 1–5 protocol including
CronCreate.
Commands
| Command | Behavior |
|---|---|
/watch start |
Default: create state, prompt user to run npm run watch:local |
/watch start --remote |
Use CronCreate polling (counts against 15/day quota — requires confirmation) |
/watch start --interval {N}m |
Set poll interval for --remote mode (default: 5m) |
/watch stop |
Stop watching, tear down cron |
/watch status |
Show watch state, last scan time, pending actions |
/watch scan |
Run a single scan now (manual trigger) |
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.
- 1mo ago First seen · 323 lines · 70 tokens per session scan A 6fbeda8981a8
watch is a skill published in the GitHub repository SethGammon/Citadel (924 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 2,992 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
compose-org
Run a task as an evolved multi-agent ORG using the installed liquid-org framework — where YOU (the running Claude) embody the org: you ask liquid-org which proven team topology + specialist personas to use (retrieved from its evolved pool, or assembled fresh), then dispatch ONE SUBAGENT PER TALENT to play each role…
liquid-rank
Rank the available skills by RELEVANCE to the current task, on demand, using liquid-org's read-only hermes skill ranker. This is an EXPLICIT, OPT-IN selector you invoke WHEN you want help choosing the most relevant skill for what you're doing — it is NOT default, automatic skill selection, and it does NOT decide for…
present-gate
First-officer gate-presentation rendering — the captain-facing gate-review template and assembly rules, including workflow-owned finding labels. Invoke at the gate point after the FO has decided a stage must be presented.
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
prototype
Use when asked to prototype one design question through a cheap logic or UI experiment, including button-driven state-model checks. Not for polished artifacts: use polished-web-prototype.
contexts
Use when the user says "get context on X", "how does X work", or wants architectural orientation before coding.