lading is a data-generation and load-testing tool that measures the performance and resource behavior of long-running programs by sending them repeatable synthetic workloads. Developers and performance engineers use it to test daemons and other complex programs across different protocols, including in Datadog Agent regression testing. The catalogue skills and instruction support working with lading.
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-optimize-reviewnpx skills add DataDog/lading --skill lading-optimize-reviewgit 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-optimize-review)<a href="https://agentmods.dev/skills/datadog/lading/lading-optimize-review"><img src="https://agentmods.dev/badge/skills/datadog/lading/lading-optimize-review.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.00026 | $0.01909 |
| Opus 5 | $0.00013 | $0.00955 |
| Sonnet 5 | $0.00005 | $0.00382 |
| Haiku 4.5 | $0.00003 | $0.00191 |
Grade B, and why
lading-optimize-review scanned grade B 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 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
allowed-tools: Bash(cat:*) Bash(sample:*) Bash(samply:*) Bash(cargo:*) Bash(ci/*:*) Bash(hyperfine:*) Bash(*/payloadtool:*) Bash(tee:*) Read Glob Grep How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimization Patch Review
A rigorous 5-persona peer review system for optimization patches in lading. Requires unanimous approval backed by concrete benchmark data. Duplicate Hunter persona prevents redundant work.
Role: Judge
Review is the decision-maker. It does NOT record results.
Review judges using benchmarks and 5-persona review, then returns a structured report.
Outcomes
| Outcome | Votes | Action |
|---|---|---|
| APPROVED | 5/5 APPROVE | Return APPROVED report |
| REJECTED | Any REJECT | Return REJECTED report |
Arguments
This skill requires 5 positional arguments passed by the caller:
| Arg | Field | Example | Used for |
|---|---|---|---|
$ARGUMENTS[0] |
bench | trace_agent |
cargo criterion --bench flag |
$ARGUMENTS[1] |
fingerprint | ci/fingerprints/trace_agent_v04/lading.yaml |
payloadtool config path |
$ARGUMENTS[2] |
file | lading_payload/src/trace_agent/v04.rs |
report + duplicate check |
$ARGUMENTS[3] |
target | V04::to_bytes |
report |
$ARGUMENTS[4] |
technique | buffer-reuse |
report + duplicate check |
If any argument is missing -> REJECT. All 5 are required.
Generate Report ID
Derive the id from the file and technique arguments:
- Take the filename stem from
$ARGUMENTS[2](e.g.lading_payload/src/trace_agent/v04.rs→trace-agent-v04) - Append the technique
$ARGUMENTS[4](e.g.buffer-reuse) - Join with
-→trace-agent-v04-buffer-reuse
Use this id in the report.
Phase 1: Benchmark Execution
Step 1: Read Baseline Data
Read the baseline benchmark files captured:
/tmp/criterion-baseline.log— micro-benchmark baseline/tmp/baseline.json— macro-benchmark timing baseline/tmp/baseline-mem.txt— macro-benchmark memory baseline
If baseline data is missing -> REJECT. Baselines must be captured before any code change and before this gets invoked.
Step 2: Run Post-Change Micro-benchmarks
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.
- 5d ago First seen · 203 lines · 26 tokens per session scan B 6a24944dc121
lading-optimize-review is a skill published in the GitHub repository DataDog/lading (98 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 1,909 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). 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…