agent-lightning: Skill for Codex

.agents/skills/release/SKILL.md

release is a skill for Codex from microsoft/agent-lightning. It costs 63 tokens per session (2,661 once invoked), scanned A, original, MIT.

A procedure for publishing stable versions of Agent Lightning, a toolkit for optimizing coding agents. It covers version changes, pull-request checks, merging, tags, PyPI publishing, and versioned documentation.

In plain words
What is it for?
Use it when planning, creating, checking, or explaining an Agent Lightning release. Nightly TestPyPI builds follow a separate process.
Why use it?
A merged pull request alone does not publish a stable release. The procedure helps verify the repository and follow the steps that make the package and its documentation public.

Skill for Codex ✓ vendor

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is microsoft/agent-lightning's own configuration. It tells Codex how to work on agent-lightning itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agent-lightning configures →

About the project

Agent Lightning is a lightweight framework for training AI agents through reinforcement learning with real agent harnesses, tools, contexts, control flows, and environments. Researchers and engineers use it to collect agent interactions, train policies, and run rollouts locally or as Kubernetes jobs. Its catalogue add-ons provide workflows for using and training agents with Agent Lightning.

microsoft/agent-lightning · 18,906 stars · on GitHub · microsoft.github.io

Reuse

Borrowing it

Nothing to install: this file belongs to microsoft/agent-lightning. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/microsoft/agent-lightning/main/.agents/skills/release/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/microsoft/agent-lightning

Made for: Codex.

Wrote 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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/agent-lightning/release/github.svg)](https://agentmods.dev/skills/microsoft/agent-lightning/release)
Your own site
<a href="https://agentmods.dev/skills/microsoft/agent-lightning/release"><img src="https://agentmods.dev/badge/skills/microsoft/agent-lightning/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/agent-lightning/release"><img src="https://agentmods.dev/badge/skills/microsoft/agent-lightning/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,661 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Snyk pass 7 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.02661
Opus 5.5 $0.00025 $0.01064
Sonnet 5.5 $0.00013 $0.00532
Haiku 4.5 $0.00006 $0.00266

Measured 2mo ago against content hash 44be3b95bec6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.agents/skills/release/SKILL.md · 239 lines

How it starts

The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Agent Lightning

Merging a pull request does not publish a stable release. Stable publication is triggered only by pushing a v* tag to the canonical repository; the tagged commit is what gets tested, built, and uploaded. That same tag push also deploys versioned documentation and moves the public stable alias, so a release has two public side effects, not one.

Establish the release state

  1. Confirm the repository root, clean working tree, current branch, and remotes.
  2. Resolve the canonical OWNER/REPO, its default branch, and its permitted merge methods with gh repo view OWNER/REPO --json nameWithOwner,defaultBranchRef,mergeCommitAllowed,rebaseMergeAllowed,squashMergeAllowed. Identify the local remotes for that repository and the contributor fork by their URLs; do not assume particular remote names or merge settings.
  3. Inspect the release contract in:
    • .github/workflows/pypi-release.yml
    • .github/workflows/docs.yml
    • .github/workflows/tests.yml
    • scripts/bump_version.sh
    • pyproject.toml
    • agentlightning/__init__.py
  4. Confirm the canonical default branch is already green before branching from it. Resolve its current commit with gh api repos/OWNER/REPO/commits/<default-branch> and inspect that commit's check runs; a general recent-run listing can omit or mix commits. A release branch inherits every failure that main is carrying.
  5. Query the canonical repository's tags and compare them with the versions published at https://pypi.org/pypi/agentlightning/json. Confirm the target version exists in neither place, and stop for an explicit release decision when either of these holds:
    • A tag exists with no matching PyPI version. A published version is immutable, and its tag must never be reused or moved. A tag that never published is a different situation and still needs a human decision, informed by why it did not publish. See "Recovering a tag that never published" below.
    • The proposed bump would skip a version that was tagged but never published.
  6. Treat verified PyPI trusted-publisher configuration for the canonical repository and pypi-release.yml as a prerequisite. If it cannot be inspected directly, require confirmation from an authorized PyPI project owner before pushing the release tag.

Read the full file on GitHub · 239 lines

Files

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.

Changes

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.

  1. 2mo ago First seen · 239 lines · 63 tokens per session scan A 44be3b95bec6

Subscribe to this mod's changes

release is a skill published in the GitHub repository microsoft/agent-lightning (18,906 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 2,661 once invoked, about $0.0003 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.

Related

release compared with skills from other repositories

release next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
releasemicrosoft/agent-lightningSkill19kyesterdayMITA63Codex
ship-featureopenonion/connectonionSkill1.5kyesterdayApache-2.0C46Claude Code, Codex
release-prepmassgen/MassGenSkill1.1k4mo agononeA25Claude Code, Codex
massgen-release-documentermassgen/MassGenSkill1.1k4mo agononeA42Claude Code, Codex
apply-patchagentscope-ai/agentscope-javaSkill6.3kyesterdayApache-2.0A38Claude Code, Codex
git-checkpointagentscope-ai/agentscope-javaSkill6.3kyesterdayApache-2.0A39Claude Code, Codex
commitopenonion/connectonionSkill1.5kyesterdayApache-2.0A26Claude Code, Codex