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/abilityai/cornelius/domain-watchnpx skills add Abilityai/cornelius --skill domain-watchgit clone --depth 1 https://github.com/Abilityai/corneliusWrote 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/abilityai/cornelius/domain-watch)<a href="https://agentmods.dev/skills/abilityai/cornelius/domain-watch"><img src="https://agentmods.dev/badge/skills/abilityai/cornelius/domain-watch.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.1 | $0.00052 | $0.07457 |
| Opus 5 | $0.00026 | $0.03728 |
| Sonnet 5 | $0.00010 | $0.01491 |
| Haiku 4.5 | $0.00005 | $0.00746 |
Grade A, and why
domain-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 6d 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 — 421 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Watch
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.domain-watch vX.Y — recent: <summary>. Then proceed.
Autonomous perception layer. Each scheduled run scans configured domains for new KB notes, checks gap resonance with the Thinking Registry, probes external signals via web search, and auto-activates HIGH/MEDIUM proposals directly into the Thinking Registry. LOW/NONE signals are logged only.
Design principle: Perceive, score, activate. Human reviews the Watch Log post-run.
State Dependencies
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| Watching Registry | Brain/05-Meta/Watching/WATCHING-REGISTRY.md |
✓ | ✓ | Active domain list + last scan dates |
| Domain Configs | Brain/05-Meta/Watching/[domain-slug].md |
✓ | ✓ | Per-domain PIRs, queries, baseline counts |
| Watch Log | Brain/05-Meta/Watching/WATCH-LOG.md |
✓ | ✓ | Append-only proposals and scan history |
| Thinking Registry | Brain/05-Meta/Thinking/THINKING-REGISTRY.md |
✓ | Gap resonance check (read-only) | |
| Local Brain Search | resources/local-brain-search/ |
✓ | Semantic search for KB notes | |
| Session Changelogs | Brain/05-Meta/Changelogs/ |
✓ | Run log |
Prerequisites
- Watching Registry exists at
Brain/05-Meta/Watching/WATCHING-REGISTRY.md - At least one active domain seeded (see Seeding section below)
- Local Brain Search index up-to-date
Process
Step 1: Get Date and Load Registry
date -u '+%Y-%m-%d %H:%M UTC'
Always use date -u: the Trinity container clock runs in a non-UTC local zone (observed UTC-4), so a bare date mislabels the scan time and a git log --since given a UTC timestamp silently shifts the change window by hours. When computing "changed since last scan" with git, pass --since with an explicit offset (e.g. --since="2026-07-13T00:30:00+00:00"). The same trap applies to find -newermt "<datetime>" - it parses the timestamp in CONTAINER-LOCAL time, so a bare UTC scan time silently shifts the window ~4h forward and returns an empty/short list (bit Run 812). Prefer git log --since with the explicit +00:00 offset for the changed-since check; if using find, append an explicit offset (-newermt "2026-07-13 20:30 +0000", GNU find).
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.
- 6d ago First seen · 421 lines · 52 tokens per session scan A 8f2ea25682c9
domain-watch is a skill published in the GitHub repository Abilityai/cornelius (106 stars, last pushed 13d ago), licensed MIT. It adds 52 tokens to every session and 7,457 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…