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/create-prnpx skills add latitude-dev/latitude-llm --skill create-prgit 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/create-pr)<a href="https://agentmods.dev/skills/latitude-dev/latitude-llm/create-pr"><img src="https://agentmods.dev/badge/skills/latitude-dev/latitude-llm/create-pr.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 | $0.00011 | $0.01098 |
| Opus 5 | $0.00005 | $0.00549 |
| Sonnet 5 | $0.00002 | $0.00220 |
| Haiku 4.5 | $0.00001 | $0.00110 |
Grade A, and why
create-pr 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 5d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Description Guidelines
The work is done. Now, create a new PR for the current changes. If you're not on a new branch yet, create one first. Then, create the PR. Treat the changes as a real deliverable. The description is the first thing anyone reading this work will see, and most readers will not read the diff line by line.
Audience
Write for someone who:
- Is a developer on this team
- Already knows this repository and its existing architecture
- Has not seen this work before
You don't need to explain the codebase, the framework, or how things generally work in this system. You do need to explain everything new that this PR introduces — concepts, entities, flows, behaviors — clearly enough that the reader understands the change without opening the diff.
Cover only what's in this PR. If it's part of a larger effort (MVP, migration, refactor), one short line of framing is enough. Don't restate the whole project.
Title
The title is a one-line summary of the change. Specific, declarative, imperative mood.
- Good:
Add alert incident lifecycle and worker pipeline - Bad:
Alert work/Various improvements/Updates to alerts module
If the repo uses a prefix convention (feat:, fix:, scoping like [backend]), match it.
What the description must convey
Every PR description, regardless of size, has to answer:
- What this PR does — the actual change, in plain language
- Why it exists — the problem, motivation, or unblock (skip only if the title makes it self-evident)
Beyond those two, include whatever else the reader needs to actually understand the change:
- New domain concepts introduced (entities, events, jobs, statuses, etc.): what they are, when they're created, who produces and consumes them
- Non-obvious decisions: trade-offs, why an alternative was rejected, schema or concurrency choices that aren't visible from the diff
- Deliberate scope cuts and known follow-ups
- Anything a reviewer would otherwise have to reverse-engineer from the code
- How the change was tested or validated, when relevant
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.
- 5d ago First seen · 86 lines · 11 tokens per session scan A 24f469703362
create-pr is a skill published in the GitHub repository latitude-dev/latitude-llm (4,619 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 1,098 once invoked, about $0.0001 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.