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.
Borrowing it
Nothing to install: this file belongs to latitude-dev/latitude-llm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/latitude-dev/latitude-llm/development/.agents/skills/managing-maintenance-windows/SKILL.mdgit 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/managing-maintenance-windows)<a href="https://agentmods.dev/skills/latitude-dev/latitude-llm/managing-maintenance-windows"><img src="https://agentmods.dev/badge/skills/latitude-dev/latitude-llm/managing-maintenance-windows/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/latitude-dev/latitude-llm/managing-maintenance-windows"><img src="https://agentmods.dev/badge/skills/latitude-dev/latitude-llm/managing-maintenance-windows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium Data Exfiltration · line 31 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 52 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00048 | $0.00682 |
| Opus 5 | $0.00024 | $0.00341 |
| Sonnet 5 | $0.00010 | $0.00136 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
managing-maintenance-windows scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -I https://console.latitude.so/ How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing maintenance windows
Use this skill when a user asks to enable, disable, verify, or prepare Latitude's production maintenance window.
What maintenance mode does
- Maintenance mode is an ALB-level switch in
infra/lib/alb.ts. - When enabled, all public production service hostnames redirect to
https://status.latitude.so/:console.latitude.so,api.latitude.so,ingest.latitude.so, andbull-board.latitude.so. - The switch is controlled by the Pulumi production config key
enableWebMaintenanceRedirect. - Do not implement this in
apps/web: if a service is unhealthy, app-level redirects may not run.
Enable maintenance mode
From infra/:
pulumi config set enableWebMaintenanceRedirect true --stack production
pulumi preview --stack production
pulumi up --stack production
Then verify from outside the VPC:
curl -I https://console.latitude.so/
curl -I https://api.latitude.so/health
curl -I https://ingest.latitude.so/health
curl -I https://bull-board.latitude.so/
Expected result: all requests return an HTTP redirect with Location: https://status.latitude.so/.
Disable maintenance mode
From infra/:
pulumi config rm enableWebMaintenanceRedirect --stack production
pulumi preview --stack production
pulumi up --stack production
Then verify:
curl -I https://console.latitude.so/
curl -I https://api.latitude.so/health
curl -I https://ingest.latitude.so/health
curl -I https://bull-board.latitude.so/
Expected result: none of the requests redirects to https://status.latitude.so/. Services may return normal responses or auth redirects depending on the requested path.
Safety checklist
Before enabling:
- Confirm the user wants all publicly exposed production services redirected.
- Confirm
https://status.latitude.so/is live and has the relevant Better Stack maintenance or incident notice. - Run
pulumi preview --stack productionand check that the ALB HTTPS listener default action and all public host rules change from forwarding to redirecting. - Apply only after the user has approved the production change, unless they already explicitly asked to execute it.
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.
- 10d ago First seen · 79 lines · 48 tokens per session scan A ff584d5b6164
managing-maintenance-windows is a skill published in the GitHub repository latitude-dev/latitude-llm (4,632 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 682 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (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
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-notebook-execution
Execute and display Jupyter notebooks for TruLens demos and quickstarts.
trulens-evaluation-workflow
Systematically evaluate your LLM application with TruLens.
trulens-blocking-guardrails
Configure and use feedback functions as runtime blocking guardrails.
trulens-dataset-curation
Create and curate evaluation datasets with ground truth for TruLens.