Latitude is an open-source platform for monitoring AI agents by collecting execution traces, grouping failures, dispatching coding agents to make fixes, and replaying failures to verify them. Teams use it to observe agent behavior, investigate errors, and monitor whether fixes prevent regressions. The catalogue entries include skills, instructions, and an MCP server for working with Latitude.
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/latitude-dev/latitude-llm/notificationsnpx skills add latitude-dev/latitude-llm --skill notificationsgit clone --depth 1 https://github.com/latitude-dev/latitude-llmWrote 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/latitude-dev/latitude-llm/notifications)<a href="https://agentmods.dev/skills/latitude-dev/latitude-llm/notifications"><img src="https://agentmods.dev/badge/skills/latitude-dev/latitude-llm/notifications.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.00035 | $0.03266 |
| Opus 5 | $0.00017 | $0.01633 |
| Sonnet 5 | $0.00007 | $0.00653 |
| Haiku 4.5 | $0.00003 | $0.00327 |
Grade A, and why
notifications 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notifications
When to use: Adding a notification kind / group / channel, touching the notifications table or users.notification_preferences, wiring a new source event into the notification pipeline, or debugging in-app / email delivery.
Always read dev-docs/notifications.md for the full picture before editing. This skill is the action-oriented summary.
Vocabulary (and what NOT to confuse)
Four orthogonal axes — keep them straight:
| Axis | Type | Examples | Lives in |
|---|---|---|---|
| Kind | flat enum (event-type) | incident.event, incident.opened, incident.closed, wrapped.report, custom.message |
NOTIFICATION_KIND_META in @domain/notifications |
| Group | user-visible category | signals, monitors, wrapped_reports, custom_messages, personal, destinations, billing |
NOTIFICATION_GROUPS in @domain/shared |
| Topic | sub-toggle inside a group | signal.discovered, signal.escalating, signal.regressed, signal.reprioritized |
NOTIFICATION_TOPICS in @domain/shared |
| Channel | delivery surface | email, slack |
per-channel worker + registry |
AlertIncidentKind (issue.new / issue.regressed / issue.escalating) is a fifth axis — it lives inside the incident.* payload and gates the producer step at the project level. It is not a NotificationKind. The mapping today: issue.new and issue.regressed → incident.event (one-shot, endedAt = startedAt); issue.escalating → incident.opened + later incident.closed (sustained, endedAt transitions from null). The producer derives the notification kind from incident.endedAt, so adding a new sustained or eventful alert kind is purely a @domain/alerts change.
Pipeline at a glance
source domain event → domain-events worker
→ notifications:request-<group>-notifications
→ notifications:create-notification (one per recipient)
→ notification-email:send (if user prefs allow)
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 · 134 lines · 35 tokens per session scan A 70811cf27a20
notifications is a skill published in the GitHub repository latitude-dev/latitude-llm (4,629 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 3,266 once invoked, about $0.0002 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
trulens-evaluation-setup
Configure feedback functions and selectors for TruLens evaluations.
trulens-instrumentation
Instrument LLM apps with TruLens OTEL-based tracing - from setup to debugging and optimization.
trulens-evaluation-workflow
Systematically evaluate your LLM application with TruLens.
trulens-notebook-execution
Execute and display Jupyter notebooks for TruLens demos and quickstarts.
trulens-dataset-curation
Create and curate evaluation datasets with ground truth for TruLens.
trulens-blocking-guardrails
Configure and use feedback functions as runtime blocking guardrails.