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.
Borrowing it
Nothing to install: this file belongs to DataDog/lading. 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/DataDog/lading/main/.claude/skills/lading-optimize-submit/SKILL.mdgit 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-submit)<a href="https://agentmods.dev/skills/datadog/lading/lading-optimize-submit"><img src="https://agentmods.dev/badge/skills/datadog/lading/lading-optimize-submit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/datadog/lading/lading-optimize-submit"><img src="https://agentmods.dev/badge/skills/datadog/lading/lading-optimize-submit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.00922 |
| Opus 5.5 | $0.00013 | $0.00369 |
| Sonnet 5.5 | $0.00007 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
lading-optimize-submit 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 2mo 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimization Submit Workflow
Complete optimization workflow with git automation. This skill wraps /lading-optimize-hunt and handles:
- Git branch creation
- Git commit with formatted results
- Optional push and PR creation
Phase 0: Pre-flight
Run /lading-preflight first to ensure environment is ready.
Phase 1: Prepare Git Environment
# Ensure clean state on main
git checkout main && git pull
# Verify clean working directory
git status
STOP if working directory is dirty. Commit or stash changes before proceeding.
Phase 2: Hunt
Run /lading-optimize-hunt.
CRITICAL: After /lading-optimize-hunt completes, you MUST return here to Phase 3.
The hunt workflow will:
- Select and analyze optimization targets
- Capture baseline benchmarks
- Implement optimization
- Run basic ci/validate check
- Invoke /lading-optimize-review (which runs post-change benchmarks and judges)
The hunt will:
- Record the verdict in
.claude/skills/lading-optimize-hunt/assets/db.yamlafter review returns
BUT the hunt does NOT:
- Run post-change benchmarks (review does this)
- Make pass/fail decisions (review does this)
- Create git branches
- Commit changes
- Push to remote
- Create PRs
Those are the responsibility of THIS skill (lading-optimize-submit).
Phase 3: Create Optimization Branch
Create a new branch and add the changes.
# Create descriptive branch name
# Format: opt/<crate>-<technique>
# Examples:
# opt/payload-cache-prealloc
# opt/throttle-avoid-clone
# opt/syslog-buffer-reuse
git checkout -b opt/<crate>-<technique>
git add .
Using the template in .claude/skills/lading-optimize-submit/assets/commit-template.txt, commit the changes:
# Example:
git commit -m "opt: buffer reuse in syslog serialization
Replaced per-iteration format!() with reusable Vec<u8> buffer.
Target: lading_payload/src/syslog.rs::Syslog5424::to_bytes
Technique: buffer-reuse
Micro-benchmarks:
syslog_100MiB: +42.0% throughput (481 -> 683 MiB/s)
Macro-benchmarks (payloadtool):
Time: -14.5% (8.3 ms -> 7.1 ms)
Memory: -35.8% (6.17 MiB -> 3.96 MiB)
Allocations: -49.3% (67,688 -> 34,331)
Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
"
What ships with it
1 file 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.
- 2mo ago First seen · 141 lines · 33 tokens per session scan A 4fbebf2794e0
lading-optimize-submit is a skill published in the GitHub repository DataDog/lading (101 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 922 once invoked, about $0.0001 per session on Opus 5.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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.