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/mintlify-preview/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/mintlify-preview)<a href="https://agentmods.dev/skills/latitude-dev/latitude-llm/mintlify-preview"><img src="https://agentmods.dev/badge/skills/latitude-dev/latitude-llm/mintlify-preview.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.00069 | $0.00914 |
| Opus 5 | $0.00034 | $0.00457 |
| Sonnet 5 | $0.00014 | $0.00183 |
| Haiku 4.5 | $0.00007 | $0.00091 |
Grade A, and why
mintlify-preview 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 7d 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 -s -o /dev/null -w '%{http_code}\n' http://localhost:3333/ # 307 redirect to first page — fine How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mintlify docs local preview
The public product docs site lives in docs/ (docs.json + topical .mdx/.md pages). It is served locally with the Mintlify CLI (mint dev). This is the product docs site, not dev-docs/ — for durable internal domain docs see the docs skill.
TL;DR — start the server
Run from the docs/ directory (where docs.json lives), on a non-default port so it doesn't collide with the web app on 3000:
cd docs
PATH="$(ls -d "$HOME"/.nvm/versions/node/v22.*/bin 2>/dev/null | sort -V | tail -1):$PATH" mint dev --port 3333
Then open http://localhost:3333. A page at docs/<folder>/<file>.mdx is served at http://localhost:3333/<folder>/<file> (e.g. docs/monitors/overview.mdx → /monitors/overview). The server hot-reloads on edits to any .mdx/.md or docs.json.
Prefer running it in the background and tailing the output until you see ✓ preview ready.
Why the PATH prefix (node version gotcha)
Mintlify does not run on Node 25+. This repo's default/active Node is often 25, which fails with:
erro mintlify is not supported on node versions 25+ (current version 25.9.0).
The PATH=... prefix above pins an installed Node 22 LTS (from nvm) for just this command, without changing the repo's active Node. If no v22.* is installed, install one (nvm install 22) or use any LTS <25. mise/nvm activate in a child shell won't help — prefix the PATH on the command itself.
Keep the CLI current (schema gotcha)
docs.json uses current Mintlify schema features (e.g. styling.codeblocks as an object). An outdated CLI rejects valid config with:
🚨 Invalid docs.json: #.styling.codeblocks: Expected ... received 'object'
Fix by updating the CLI, not by editing docs.json (the checked-in config is correct for the real deploy):
PATH="$(ls -d "$HOME"/.nvm/versions/node/v22.*/bin 2>/dev/null | sort -V | tail -1):$PATH" mint update
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.
- 7d ago First seen · 64 lines · 69 tokens per session scan A dec8c718f655
mintlify-preview is a skill published in the GitHub repository latitude-dev/latitude-llm (4,629 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 914 once invoked, about $0.0003 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-evaluation-workflow
Systematically evaluate your LLM application with TruLens.
trulens-notebook-execution
Execute and display Jupyter notebooks for TruLens demos and quickstarts.
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.