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/releasenpx skills add DataDog/lading --skill releasegit clone --depth 1 https://github.com/DataDog/ladingWhat 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.00031 | $0.00482 |
| Opus 5 | $0.00015 | $0.00241 |
| Sonnet 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 2d 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.
- 2d ago First seen · 50 lines · 31 tokens per session scan A c3d9d23f6303
release is a skill published in the GitHub repository DataDog/lading (98 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 482 once invoked, about $0.0002 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…