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/datadog/lading/lading-preflightnpx skills add DataDog/lading --skill lading-preflightgit clone --depth 1 https://github.com/DataDog/ladingWrote 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/datadog/lading/lading-preflight)<a href="https://agentmods.dev/skills/datadog/lading/lading-preflight"><img src="https://agentmods.dev/badge/skills/datadog/lading/lading-preflight.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.00055 | $0.00453 |
| Opus 5 | $0.00028 | $0.00227 |
| Sonnet 5 | $0.00011 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade C, and why
lading-preflight scanned grade C with 2 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 3d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
| rustc not found | `curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs \| sh` | Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| rustc not found | `curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs \| sh` | How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run preflight script
.claude/skills/lading-preflight/scripts/preflight
STOP on any failure. Use the table below to suggest fixes for [X] items.
Offer suggestions then ask before proceeding
For each failed check, show the user the suggested fix from the table below and ask if they want you to run it. Do NOT automatically execute fixes — wait for user confirmation before taking action.
| Failed Check | Fix |
|---|---|
| rustc not found | curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh |
| cargo not found | Reinstall rustup |
| cargo-nextest not found | cargo install cargo-nextest |
| ci/* not executable | chmod +x ci/* |
| ci/check failed | cargo update, check dependency issues |
| payloadtool build failed | Check Rust version and dependencies |
| hyperfine not found | brew install hyperfine |
| cargo-criterion not found | cargo install cargo-criterion |
| criterion benchmarks missing | Check lading_payload/benches/ and Cargo.toml |
| payloadtool --memory-stats not supported | Rebuild payloadtool from current branch |
| git user.name not set | git config user.name "Your Name" |
| git user.email not set | git config user.email "[email protected]" |
| gh not found | brew install gh |
| aws CLI not found | brew install awscli |
| smp not found | .claude/skills/lading-preflight/scripts/install_smp |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 37 lines · 55 tokens per session scan C 46afbe689934
lading-preflight is a skill published in the GitHub repository DataDog/lading (98 stars, last pushed 6d ago), licensed MIT. It adds 55 tokens to every session and 453 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…