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 nebulae/trudi --skill trudi-watch-alertsgit clone --depth 1 https://github.com/nebulae/trudiWrote 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/nebulae/trudi/trudi-watch-alerts)<a href="https://agentmods.dev/skills/nebulae/trudi/trudi-watch-alerts"><img src="https://agentmods.dev/badge/skills/nebulae/trudi/trudi-watch-alerts/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/nebulae/trudi/trudi-watch-alerts"><img src="https://agentmods.dev/badge/skills/nebulae/trudi/trudi-watch-alerts.svg" alt="Reviewed on agentmods" width="80" 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.00029 | $0.00576 |
| Opus 5.5 | $0.00012 | $0.00230 |
| Sonnet 5.5 | $0.00006 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
trudi-watch-alerts 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 4d 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.
What it actually says
Accept a case ID and optional polling interval in seconds, for example
$trudi-watch-alerts WINDECOY-DEMO 1. Use one second when the interval is
omitted. Resolve the explicit case first, otherwise the current case directory.
Read the case instructions and $trudi-check-alerts. Confirm a producer with monitor.list_watchers; use $trudi-start-watcher if the operator requested startup and none is running. Respect an explicit exercise hold before draining alerts. Check queued alerts and any open investigation first.
Codex does not provide Claude's Monitor, TaskStop, or /loop workflow. Use the repository's read-only bin/trudi-alert-waiter.py in one-shot mode:
python3 <repo>/bin/trudi-alert-waiter.py --case-id <CASE> --cases-root <CASES_ROOT> --since-seq <CURSOR> --interval <SECONDS> --timeout 30
This interval polls the local alert queue. Run the full check-alerts workflow when work arrives, not once per idle second. Sensor detection, collection, and investigation have their own latency; a one-second poll is not a promise of one-second containment or completed findings.
Run it with exec_command, then poll that same session with write_stdin if it yields. Wait at most 30 seconds per poll so operator input remains responsive. On ALERTS, execute $trudi-check-alerts. On HEARTBEAT, check producer health and continue waiting. Keep the turn active; a detached process does not wake an idle Codex agent automatically. Do not promise monitoring after ending the turn.
Keep the notification cursor separate from the completed-work cursor. Advance the waiter's in-memory CURSOR to the highest sequence it has surfaced, so a pending unacknowledged alert does not cause a tight repeat loop. Advance the case's _last_check_seq.txt only for work actually completed and acknowledged. On every wake, use monitor.check_alerts and the open investigation state to retain unfinished work; the notification cursor never acknowledges an alert. Alert files remain queued during collection, including alerts arriving while the investigation is running. Keep a pending action attached to its open investigation; avoid reopening it or issuing duplicate prompts. Send brief status updates during long waits. When the operator asks to stop, stop waiting and report pending work; the producer remains running unless the operator also requests $trudi-stop-watcher.
The signed CEF sidecar can independently apply its configured reversible containment while the analyst is idle. That is separate from the agent's investigation loop.
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.
- 4d ago First seen · 47 lines · 29 tokens per session scan A 02c7b7d63ada
trudi-watch-alerts is a skill published in the GitHub repository nebulae/trudi (67 stars, last pushed 5d ago), licensed MIT. It adds 29 tokens to every session and 576 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-10-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…