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 skills add terrene-foundation/kailash-coc-claude-py --skill 10-deployment-gitgit clone --depth 1 https://github.com/terrene-foundation/kailash-coc-claude-pyWrote 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/terrene-foundation/kailash-coc-claude-py/10-deployment-git)<a href="https://agentmods.dev/skills/terrene-foundation/kailash-coc-claude-py/10-deployment-git"><img src="https://agentmods.dev/badge/skills/terrene-foundation/kailash-coc-claude-py/10-deployment-git/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/terrene-foundation/kailash-coc-claude-py/10-deployment-git"><img src="https://agentmods.dev/badge/skills/terrene-foundation/kailash-coc-claude-py/10-deployment-git.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.00026 | $0.01581 |
| Opus 5 | $0.00013 | $0.00790 |
| Sonnet 5 | $0.00005 | $0.00316 |
| Haiku 4.5 | $0.00003 | $0.00158 |
Grade A, and why
deployment-git 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- deployment-git — 86% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDK Release & Git Workflows
Comprehensive guides for releasing the Kailash Python SDK to PyPI, managing CI/CD pipelines, deploying documentation, and Git workflow best practices.
Overview
SDK release and development infrastructure patterns for:
- PyPI package publishing (TestPyPI + production)
- CI/CD pipelines (GitHub Actions)
- Multi-platform wheel building
- Documentation deployment
- Git workflows and branching strategies
- Multi-package version coordination
Reference Documentation
Deployment Lifecycle
-
deployment-onboarding - SDK release onboarding process
- Codebase analysis (packages, build system, CI, docs)
- Structured questions for human architect
- Research current PyPI/CI best practices
- Create deployment-config.md
-
release-runbook - SDK release runbook (detailed procedures)
- Version locations for all packages (pyproject.toml + init.py)
- SDK dependency pin rules
- Version consistency verification commands
- Pre-release, build, publish, post-release step-by-step procedures
-
deployment-packages - Package release workflow
- PyPI and GitHub release process
- Multi-package coordination and publish order
- Version bumping and changelog
- CI-triggered releases
- TestPyPI validation
- Rollback procedures
-
deployment-ci - CI/CD infrastructure
- GitHub Actions workflows for Python packages
- Multi-platform wheel building
- Test matrix (Python versions x OS)
- Tag-triggered publishing pipeline
- Documentation deployment (ReadTheDocs, GitHub Pages)
- Self-hosted runner management
-
python-version-bump - Python minor-version bump playbook
- When to declare a new CPython release (3.X stable + ≥1 patch)
- 3-step recipe: pyproject classifiers → CI matrices →
uv pip install --dry-run --python 3.Xverification - Concrete file list for all 10 packages and 4 CI matrix files
- Common gotcha: stale literal version assertions in test fixtures (durable cross-surface contract pattern)
- ML stack wheel-lag guidance (torch / transformers / accelerate)
What ships with it
18 files 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.
- application-deployment.md 24 KB
- ci-runner-troubleshooting.md 8.8 KB
- deployment-ci.md 13 KB
- deployment-cloud.md 4.2 KB
- deployment-docker-quick.md 2.6 KB
- deployment-kubernetes-quick.md 3.2 KB
- deployment-onboarding.md 5.2 KB
- deployment-packages.md 4.3 KB
- deployment-patterns.md 8.6 KB
- docker-dev-env-patterns.md 10 KB
- git-release-patterns.md 5.5 KB
- git-workflow-quick.md 2.1 KB
- github-management-patterns.md 6.1 KB
- multi-package-release-wave.md 7.2 KB
- project-management.md 16 KB
- python-version-bump.md 4.9 KB
- release-runbook.md 4.6 KB
- todo-github-sync.md 14 KB
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.
- 7d ago First seen · 216 lines · 26 tokens per session scan A 3742b2f38676
deployment-git is a skill published in the GitHub repository terrene-foundation/kailash-coc-claude-py (12 stars, last pushed 23d ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,581 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
cmux-release
Prefer the /release command. It determines the new version (minor by default), gathers commits since the last tag, updates CHANGELOG.md, runs ./scripts/bump-version.sh, commits, runs ./scripts/release-pretag-guard.sh, then tags and pushes.