A release command for publishing the Kailash Python SDK and related framework packages. It also covers documentation deployment and continuous integration, the automated system that builds and checks changes.

Use it to inspect package and documentation setup, configure release onboarding, publish to PyPI, deploy documentation, and manage CI.

It gathers release settings and repository details in one process, reducing the chance of publishing or deployment steps being missed.

release — Command for Claude Code by terrene-foundation

Install

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.

Clone the repo

git clone --depth 1 https://github.com/terrene-foundation/kailash-coc-claude-py

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/release/github.svg)](https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/release)

Your own site

<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/release"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/release"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,360 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01360
Opus 5	$0.00000	$0.00680
Sonnet 5	$0.00000	$0.00272
Haiku 4.5	$0.00000	$0.00136

Measured 6d ago against content hash 5bf2ae5e6c2b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 6d 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.

.claude/commands/release.md · 123 lines

How it starts

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

/release - SDK Release Command

Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.

IMPORTANT: This is /release (BUILD repo command). /deploy is for USE repos only. See rules/zero-tolerance.md for the BUILD vs USE boundary.

Deployment Config

Read deploy/deployment-config.md at the project root. This is the single source of truth for how this SDK publishes releases.

Mode Detection

If `deploy/deployment-config.md` does NOT exist → Onboard Mode

Run the SDK release onboarding process:

Analyze the codebase
- What packages exist? (main kailash package + sub-packages like kailash-dataflow, kailash-nexus, kailash-kaizen)
- What build system? (pyproject.toml — setuptools, hatch, maturin, etc.)
- Existing CI workflows? (.github/workflows/)
- Documentation setup? (sphinx conf.py, mkdocs.yml, docs/ directory)
- Test infrastructure? (pytest config, tox, nox)
- Multi-package structure? (monorepo vs separate packages)
Ask the human
- PyPI publishing strategy: TestPyPI first? Wheel-only (proprietary)?
- API token setup: ~/.pypirc or CI secrets?
- Documentation hosting: ReadTheDocs, GitHub Pages, or other?
- CI system: GitHub Actions? Self-hosted runners?
- Multi-package versioning strategy: lockstep or independent?
- Changelog format: Keep a Changelog, conventional-changelog, or custom?
- Release cadence: on-demand, scheduled, or tag-triggered?
Research current best practices
- Use web search for current PyPI publishing guidance
- Use web search for current CI/CD patterns for Python packages
- Check current build, twine, maturin tool versions and syntax
- Do NOT rely on encoded knowledge — tools and best practices change
Create deploy/deployment-config.md
- Document all decisions with rationale
- Include step-by-step SDK release runbook
- Include rollback procedure (PyPI yank + corrective release)
- Include release checklist

Read the full file on GitHub · 123 lines

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.

6d ago First seen · 123 lines · 0 tokens per session scan A 5bf2ae5e6c2b

Subscribe to this mod's changes

release is a command published in the GitHub repository terrene-foundation/kailash-coc-claude-py (12 stars, last pushed 22d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,360 tokens. 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-09-03.

CI and CD DevOps and cloud Git and workflow Releases

publish

Publish oh-my-opencode to npm via GitHub Actions workflow.

code-yeongyu/oh-my-openagent · 12 tokens

deploy-release

Prepare and verify a staged or production deployment with rollback and smoke checks.

HoangNguyen0403/agent-skills-standard · 14 tokens

rollback

Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.

gotempsh/temps · 0 tokens

land-and-deploy

Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.

FlorianBruniaux/claude-code-plugins · 23 tokens

ci

Run CI validation, create PRs, and merge on green.

Generous-Corp/pulp · 14 tokens

devops

You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.

samibs/skillfoundry · 0 tokens