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/release/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/release)<a href="https://agentmods.dev/skills/datadog/lading/release"><img src="https://agentmods.dev/badge/skills/datadog/lading/release/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/release"><img src="https://agentmods.dev/badge/skills/datadog/lading/release.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.00031 | $0.00482 |
| Opus 5.5 | $0.00012 | $0.00193 |
| Sonnet 5.5 | $0.00006 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
release 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.
What it actually says
Release process for lading
1. Determine the next version
- Read
lading/Cargo.tomlandCHANGELOG.mdto find the current version and unreleased changes. - If the user hasn't specified a version, suggest one based on semver:
- Breaking changes in the unreleased section -> bump minor (we're pre-1.0).
- Otherwise bump patch.
- Confirm the version with the user before proceeding.
2. Create a release branch
- Create a branch from main:
git checkout -b prepare-release-v<version>
3. Update CHANGELOG.md
- Read
CHANGELOG.md. - Insert a new
## Unreleasedheader (with empty subsections) above the current unreleased content. - Rename the existing unreleased content block to
## [<version>]. - Ensure there is a blank line between the new empty
## Unreleasedand## [<version>].
4. Bump version in Cargo.toml
- Edit
lading/Cargo.tomlto setversion = "<new_version>".
5. Update Cargo.lock
- Run
cargo checkto propagate the version change into the lockfile without re-resolving all dependencies.
6. Commit and create PR
- Stage
CHANGELOG.md,lading/Cargo.toml, andCargo.lock. - Commit with message:
release: v<version> - Push the branch and create a PR targeting main.
7. Tag after merge
- After the PR is merged, remind the user to tag the merge commit on main:
git checkout main && git pullgit tag -a v<version> -m "v<version>"git push origin v<version>
- NEVER use
git push --tags— always push exactly one tag at a time. - The
release.ymlGitHub Actions workflow will automatically create a GitHub Release from the tag, pulling notes from CHANGELOG.md.
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 · 50 lines · 31 tokens per session scan A c3d9d23f6303
release is a skill published in the GitHub repository DataDog/lading (101 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 482 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
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.