Borrowing it
Nothing to install: this file belongs to atlanhq/atlan-python. 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/atlanhq/atlan-python/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/atlanhq/atlan-pythonWrote 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/atlanhq/atlan-python/release)<a href="https://agentmods.dev/skills/atlanhq/atlan-python/release"><img src="https://agentmods.dev/badge/skills/atlanhq/atlan-python/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/atlanhq/atlan-python/release"><img src="https://agentmods.dev/badge/skills/atlanhq/atlan-python/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.00021 | $0.01168 |
| Opus 5.5 | $0.00008 | $0.00467 |
| Sonnet 5.5 | $0.00004 | $0.00234 |
| Haiku 4.5 | $0.00002 | $0.00117 |
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 1mo 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create SDK Release
Bumps the SDK version, generates release notes in HISTORY.md, and commits on a dedicated release branch.
Usage
/release patch— bump patch version (e.g., 9.2.1 → 9.2.2)/release minor— bump minor version (e.g., 9.2.1 → 9.3.0)/release major— bump major version (e.g., 9.2.1 → 10.0.0)/release 9.3.0— set an explicit version
If no argument is provided, default to patch.
Instructions
1. Determine the new version
Read the current version from pyatlan/version.txt. Parse the argument to compute the new version:
patch: increment the third number, e.g.,9.2.1→9.2.2minor: increment the second number, reset patch, e.g.,9.2.1→9.3.0major: increment the first number, reset minor and patch, e.g.,9.2.1→10.0.0- If the argument matches a semver pattern (e.g.,
9.3.0), use it directly
Confirm the new version with the user before proceeding.
2. Gather changes since last release
Always gather from origin/main — that's where PRs are merged. The current working branch is irrelevant here.
Step 1 — find the last release commit on main and list everything since it:
git fetch origin main --quiet
git log --oneline $(git log --oneline origin/main | grep "\[release\]" | head -1 | awk '{print $1}')..origin/main
Step 2 — extract PR numbers from merge commits and fetch details for each:
git log --oneline $(git log --oneline origin/main | grep "\[release\]" | head -1 | awk '{print $1}')..origin/main | grep "Merge pull request" | grep -oE '#[0-9]+' | tr -d '#'
Then for each PR number, run:
gh pr view <number> --json title,labels,body,mergedAt
If gh is not authenticated, fall back to the commit subjects alone — do NOT skip this step or silently use an empty list. Note any PRs you couldn't fetch so the user knows the notes may be incomplete.
Step 3 — also run this to catch non-merge commits (direct pushes, fixups, etc.):
git log --oneline --no-merges $(git log --oneline origin/main | grep "\[release\]" | head -1 | awk '{print $1}')..origin/main
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.
- 1mo ago First seen · 145 lines · 21 tokens per session scan A e9fe52e5deae
release is a skill published in the GitHub repository atlanhq/atlan-python (21 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 1,168 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
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
cli-release
Release and recover first-party Composio CLI binaries through Build CLI Binaries, including automatic beta builds, promote-stable dispatches, beta-tag selection, asset and installation verification, and failed release recovery. Use when a contributor asks to build a CLI beta, publish or promote a stable CLI version…
config-loading-precedence
How Xberg resolves config: CLI and server/MCP precedence, file walk-up, inline JSON, overrides. Use when adding a setting or one does not take effect.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
azure-identity-py
Azure Identity SDK for Python authentication with Microsoft Entra ID. Use for DefaultAzureCredential, managed identity, service principals, and token caching. Triggers: "azure-identity", "DefaultAzureCredential", "authentication", "managed identity", "service principal", "credential".
m365-agents-py
Microsoft 365 Agents SDK for Python. Build multichannel agents for Teams/M365/Copilot Studio with aiohttp hosting, AgentApplication routing, streaming responses, and MSAL-based auth. Triggers: "Microsoft 365 Agents SDK", "microsoftagents", "AgentApplication", "startagentprocess", "TurnContext", "Copilot Studio…