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 cuesoftinc/oss-engineering-standards --skill cuelabs-delivery-standardgit clone --depth 1 https://github.com/cuesoftinc/oss-engineering-standardsWrote 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/cuesoftinc/oss-engineering-standards/cuelabs-delivery-standard)<a href="https://agentmods.dev/skills/cuesoftinc/oss-engineering-standards/cuelabs-delivery-standard"><img src="https://agentmods.dev/badge/skills/cuesoftinc/oss-engineering-standards/cuelabs-delivery-standard/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/cuesoftinc/oss-engineering-standards/cuelabs-delivery-standard"><img src="https://agentmods.dev/badge/skills/cuesoftinc/oss-engineering-standards/cuelabs-delivery-standard.svg" alt="Reviewed on agentmods" width="80" 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.00061 | $0.00573 |
| Opus 5 | $0.00030 | $0.00287 |
| Sonnet 5 | $0.00012 | $0.00115 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
cuelabs-delivery-standard 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 12d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CueLABS Delivery Standard
Standardize delivery around the repository's real, build-ready surfaces. Keep CI uniform without creating jobs for backends, mobile apps, or deploy targets that do not exist yet.
Read the relevant references
- Read references/cloud-and-ci.md for CueLABS cloud policy, GitHub Actions, release gating, versions, and fleet parity.
- Read references/containers-and-deploy.md for Docker, Compose, ports, Helm, Terraform, and cleanup.
- Read references/telemetry-and-environment.md for OpenTelemetry and environment-variable conventions.
Workflow
- Inspect
.cuelabs/project.yaml, real manifests, workflows, build scripts, container files, deploy definitions, and repository documentation. - Classify every surface as build-ready or not build-ready from executable evidence, not roadmap text.
- Build a job matrix from build-ready surfaces only.
- Compare shared jobs with the current CueLABS canonical shape. Keep repository variation in package/build scripts rather than duplicated workflow logic.
- Verify current official action versions from their primary release sources whenever a workflow is changed.
- Apply least-privilege permissions, concurrency cancellation, named steps, deterministic dependency installation, and failure artifact retention.
- Keep website rollout, API release, and self-host deployment paths distinct.
- Validate every changed layer with the native tool:
- workflow syntax and repository checks;
- container build or configuration validation;
helm lintandhelm template;- Terraform formatting and validation;
- service health/readiness behavior.
Guardrails
- Do not add an API or mobile CI job before that surface is build-ready.
- Do not deploy from a pull request.
- Do not add a release workflow before the deployment phase is approved.
- Do not grant broad
GITHUB_TOKENpermissions by default. - Do not introduce a second environment-variable name for an existing cross-repository concept.
- Do not embed secrets in workflows, images, manifests, examples, or logs.
- Do not claim a deployment succeeded without checking its terminal state.
What ships with it
4 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.
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.
- 12d ago First seen · 60 lines · 61 tokens per session scan A d1c2b17f92c9
cuelabs-delivery-standard is a skill published in the GitHub repository cuesoftinc/oss-engineering-standards (2 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 573 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
gear
Managing dependencies, CI/CD, advanced GitHub Actions workflows, containers, secrets, and operational config. Use for build, workflow, or environment work.
glab-cli
GitLab CLI (glab) reference and workflow for repository, merge request, issue, CI/CD, release, and API operations across GitLab.com and self-managed or dedicated instances. Use when Codex needs to run or explain glab commands, usually by relying on the current glab context first, and only falling back to git remote -v…
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.
devops-zeroclaw-coordination-rules
ZEROCLAW COORDINATION RULES — extracted from roles.json deepPrompt for devops.
dockerized-service-release-deployment-workflow
Create a Dockerized-service release contract with clean GitHub Actions builds, main-anchored tags, immutable digest manifests, published-release deployments, production approval, health checks, and exact-digest rollback.