Borrowing it
Nothing to install: this file belongs to DuqueOM/ML-MLOps-Portfolio. 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/DuqueOM/ML-MLOps-Portfolio/main/.devin/skills/release-checklist/SKILL.mdgit clone --depth 1 https://github.com/DuqueOM/ML-MLOps-PortfolioWrote 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/duqueom/ml-mlops-portfolio/release-checklist)<a href="https://agentmods.dev/skills/duqueom/ml-mlops-portfolio/release-checklist"><img src="https://agentmods.dev/badge/skills/duqueom/ml-mlops-portfolio/release-checklist.svg" alt="Measured on agentmods" height="20"></a>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.00017 | $0.01648 |
| Opus 5 | $0.00009 | $0.00824 |
| Sonnet 5 | $0.00003 | $0.00330 |
| Haiku 4.5 | $0.00002 | $0.00165 |
Grade A, and why
release-checklist scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Bash(curl:*) How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Checklist
Pre-Release Verification
Code Quality
- All CI checks passing (lint, test, build)
- Coverage >= 90% lines, >= 80% branches
- No TODO/FIXME items in critical paths
- Type hints on all public functions
Model Quality
- Quality gates passing for all services
- Fairness checks passed (DIR >= 0.80)
- SHAP consistency verified
- No data leakage detected
Infrastructure
- Terraform plan shows no unexpected changes
- tfsec/checkov clean (no HIGH/CRITICAL findings)
- Secrets rotated if approaching expiry
Documentation
- ADRs up to date for any new decisions
- Service READMEs updated with new metrics
- AGENTS.md updated if new invariants
- CHANGELOG.md updated
Version Tagging
# Update version
export VERSION=v{MAJOR}.{MINOR}.{PATCH}
# Tag and push
git tag -a ${VERSION} -m "Release ${VERSION}: {summary}"
git push origin ${VERSION}
Build and Push Images
# For each service
for SERVICE in service-a service-b service-c; do
# GCP Artifact Registry
docker build -t ${GCP_REGISTRY}/${SERVICE}:${VERSION} ${SERVICE}/
docker push ${GCP_REGISTRY}/${SERVICE}:${VERSION}
# AWS ECR
docker build -t ${AWS_REGISTRY}/${SERVICE}:${VERSION} ${SERVICE}/
docker push ${AWS_REGISTRY}/${SERVICE}:${VERSION}
done
Deploy to GCP
# Update overlays (production environment for release)
# k8s/overlays/gcp-prod/kustomization.yaml → newTag: ${VERSION} (CI replaces with @sha256 digest)
kubectl apply -k k8s/overlays/gcp-prod/
kubectl rollout status deployment --all -n {namespace} --timeout=300s
Deploy to AWS
# Update overlays (production environment for release)
# k8s/overlays/aws-prod/kustomization.yaml → newTag: ${VERSION} (CI replaces with @sha256 digest)
kubectl apply -k k8s/overlays/aws-prod/
kubectl rollout status deployment --all -n {namespace} --timeout=300s
Post-Deploy Verification
Both Clouds
-
/healthreturning 200 on all services -
/predictreturning valid predictions -
/metricsbeing scraped by Prometheus - Grafana dashboards showing new version
- No P1/P2 alerts in AlertManager
- HPA functioning (correct replica counts)
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.
- 8d ago First seen · 188 lines · 17 tokens per session scan A 67372e71625d
release-checklist is a skill published in the GitHub repository DuqueOM/ML-MLOps-Portfolio (5 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 1,648 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
publish-plugins
(project) Use when editing any file under skills/ or plugins/ to bump the plugin version and check the manifests.
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.
land-and-deploy
Land and deploy workflow. (gstack).
publish-site
Versioned site deploys to GitHub/Cloudflare/Netlify Pages.
maintainer-release-ops
Maintainer release and milestone operating workflow. Use when a maintainer wants to plan a release, assess milestone health, coordinate release blockers, or generate a release-focused review brief.
ecspresso
ECS deployment tool - deploy, manage, and troubleshoot ECS services.