built-in-metrics SKILL.md skillA
built-in-metrics from launchdarkly/ai-tooling is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add launchdarkly/ai-tooling/built-in-metrics@v1.0.0-experimentalPins v1.0.0-experimental in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- launchdarkly/ai-tooling
- Path
skills/agentcontrol/built-in-metrics/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.0-experimental, committed May 22, 2026
- First version recorded
- May 21, 2026
- Size
- 12,798 bytes
- Repository stars
- 29
- License
- a license file GitHub does not identify
Instrument an existing codebase with LaunchDarkly config tracking. Walks the four-tier ladder (managed runner → provider package → custom extractor + trackMetricsOf → raw manual) and picks the lowest-ceremony option that still captures duration, tokens, and success/error.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Agent Metrics Instrumentation
You're using a skill that wires LaunchDarkly agent metrics around an existing provider call. Your job is to audit what's already there, pick the right tier from the ladder below, and implement it with the **least ceremony that still captures the metrics the Monitoring tab needs** (duration, input/output tokens, success/error, plus TTFT when streaming).
The single most important thing to get right: **default to the highest tier that fits the shape of the call**. Going lower ("just write the manual tracker calls") looks flexible but costs you drift, missed metrics, and legacy patterns the SDKs have moved past.
## The four-tier ladder
This is the order the official SDK READMEs (Python core, Node core, and every provider package) recommend. Walk from the top and stop at the first tier that fits:
| Tier | Pattern | Use when | Tracks automatically |
|------|---------|----------|----------------------|
…Read the whole file at its exact version.
How to install
mdr add launchdarkly/ai-tooling/built-in-metrics@sha256:09004c0691898e93The line at the top of this page pins the label v1.0.0-experimental, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ouhin2vqvtru36mt)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 21, 2026 and May 22, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0-experimental latest | 2026-05-22 | add614f | 12,798 B | A | view · diff |
| v1.0.0-experimental | 2026-05-21 | e6ab09b | 12,804 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12798 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
launchdarkly/ai-tooling · 29 stars · license a license file GitHub does not identify · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ouhin2vqvtru36mt GET https://markdownregistry.com/api/v1/resolve?ref=launchdarkly/ai-tooling/built-in-metrics GET https://markdownregistry.com/api/v1/blob/09004c0691898e934813e72a7837035d36a612caf910c06ef31756c241c3d9d7
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.