push-to-registry

push-to-registry is a skill for Claude Code, Codex from eric861129/SKILLS_All-in-one. It costs 40 tokens per session (1,195 once invoked), scanned B, a copy of push-to-registry, MIT.

A Packer setup that records build details in HCP Packer Registry, a service for tracking versions and managing the lifecycle of machine images. It records metadata, not the image files themselves.

In plain words
What is it for?
Use it when connecting Packer image builds to HCP Packer Registry for build tracking and image governance.
Why use it?
It gives teams a central record of which images were built and helps manage their versions over time.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when connecting Packer image builds to HCP Packer Registry for build tracking and image governance.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/eric861129/skills_all-in-one/push-to-registry
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.

Any agent
npx skills add eric861129/SKILLS_All-in-one --skill push-to-registry
Clone the repo
git clone --depth 1 https://github.com/eric861129/SKILLS_All-in-one

Made for: Claude Code, Codex.

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.

agentmods badge for push-to-registry

README.md
[![agentmods](https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/push-to-registry/github.svg)](https://agentmods.dev/skills/eric861129/skills_all-in-one/push-to-registry)
Your own site
<a href="https://agentmods.dev/skills/eric861129/skills_all-in-one/push-to-registry"><img src="https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/push-to-registry/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.

agentmods 80×15 button for push-to-registry

Your own site · 80×15
<a href="https://agentmods.dev/skills/eric861129/skills_all-in-one/push-to-registry"><img src="https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/push-to-registry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,195 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 97% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.01195
Opus 5 $0.00020 $0.00598
Sonnet 5 $0.00008 $0.00239
Haiku 4.5 $0.00004 $0.00120

Measured 9d ago against content hash e49441146d78, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade B, and why

push-to-registry scanned grade B 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 9d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

"sudo apt-get update",
Origin

This is a copy

97% identical to push-to-registry — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

public/SKILLS/Infrastructure & Cloud/push-to-registry/SKILL.md · 204 lines

How it starts

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

Push to HCP Packer Registry

Configure Packer templates to push build metadata to HCP Packer registry.

Reference: HCP Packer Registry

Note: HCP Packer is free for basic use. Builds push metadata only (not actual images), adding minimal overhead (<1 minute).

Basic Registry Configuration

packer {
  required_version = ">= 1.7.7"
}

variable "image_name" {
  type    = string
  default = "web-server"
}

locals {
  timestamp = regex_replace(timestamp(), "[- TZ:]", "")
}

source "amazon-ebs" "ubuntu" {
  region        = "us-west-2"
  instance_type = "t3.micro"

  source_ami_filter {
    filters = {
      name = "ubuntu/images/*ubuntu-jammy-22.04-amd64-server-*"
    }
    most_recent = true
    owners      = ["099720109477"]
  }

  ssh_username = "ubuntu"
  ami_name     = "${var.image_name}-${local.timestamp}"
}

build {
  sources = ["source.amazon-ebs.ubuntu"]

  hcp_packer_registry {
    bucket_name = var.image_name
    description = "Ubuntu 22.04 base image for web servers"

    bucket_labels = {
      "os"   = "ubuntu"
      "team" = "platform"
    }

    build_labels = {
      "build-time" = local.timestamp
    }
  }

  provisioner "shell" {
    inline = [
      "sudo apt-get update",
      "sudo apt-get upgrade -y",
    ]
  }
}

Authentication

Set environment variables before building:

export HCP_CLIENT_ID="your-service-principal-client-id"
export HCP_CLIENT_SECRET="your-service-principal-secret"
export HCP_ORGANIZATION_ID="your-org-id"
export HCP_PROJECT_ID="your-project-id"

packer build .

Create HCP Service Principal

  1. Navigate to HCP → Access Control (IAM)
  2. Create Service Principal
  3. Grant "Contributor" role on project
  4. Generate client secret
  5. Save client ID and secret

Registry Configuration Options

bucket_name (required)

The image identifier. Must stay consistent across builds!

bucket_name = "web-server"  # Keep this constant

bucket_labels (optional)

Metadata at bucket level. Updates with each build.

Read the full file on GitHub · 204 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.

  1. 9d ago First seen · 204 lines · 40 tokens per session scan B e49441146d78

Subscribe to this mod's changes

push-to-registry is a skill published in the GitHub repository eric861129/SKILLS_All-in-one (52 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 1,195 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). It is 97% identical to push-to-registry, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

operate-pi-dispatch

How to operate a pi-dispatch deployment through its tools, and how to use the operator-confirm gates on the write tools (changing limits, adding/editing/deleting triggers).

edgehero/pi-dispatch · 41 tokens

deno-knowledge-patch

Use this skill when choosing current Deno runtime APIs, CLI options, configuration, dependency behavior, Node compatibility, or deployment workflows. Open the topic reference before changing a project because several commands, flags, APIs, and defaults changed more than once.

Nevaberry/nevaberry-plugins · 9 tokens

aws-cdk-knowledge-patch

Load this skill when changing, reviewing, debugging, or upgrading AWS CDK applications, construct libraries, CLI integrations, or synthesized CloudFormation templates.

Nevaberry/nevaberry-plugins · 11 tokens

aws-sdk-knowledge-patch

Use this skill when upgrading an AWS SDK or CLI, changing a supported runtime, configuring shared SDK behavior, or implementing one of the service APIs in the reference index. Identify the language, SDK major version, runtime, service, and deployment environment before applying the guidance.

Nevaberry/nevaberry-plugins · 9 tokens

azure-knowledge-patch

Use this skill for Azure infrastructure, Azure CLI, Azure PowerShell, Terraform AzureRM or AzAPI, Bicep, identity SDK, Microsoft Entra, networking, compute, containers, data services, storage, Key Vault, governance, and service lifecycle work.

Nevaberry/nevaberry-plugins · 8 tokens

chrony-knowledge-patch

Skill "chrony-knowledge-patch" from Nevaberry/nevaberry-plugins, covering chrony 4.7–4.8 knowledge patch, reference index, using this patch, breaking changes and upgrade checks and configuration and build compatibility.

Nevaberry/nevaberry-plugins · 9 tokens