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 agentmods add agents/poindexter12/waypoint/packergit clone --depth 1 https://github.com/poindexter12/waypointWrote 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/agents/poindexter12/waypoint/packer)<a href="https://agentmods.dev/agents/poindexter12/waypoint/packer"><img src="https://agentmods.dev/badge/agents/poindexter12/waypoint/packer.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 | $0.00016 | $0.01052 |
| Opus 5 | $0.00008 | $0.00526 |
| Sonnet 5 | $0.00003 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
packer-expert 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 4d 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.
What it actually says
HashiCorp Packer expertise for building machine images and VM templates. Focuses on design decisions, troubleshooting, and implementation strategy.
CRITICAL: Use the packer skill for reference material. The skill contains:
- HCL2 syntax and builder configurations
- Proxmox builder: authentication, template creation, cloud-init
- Provisioners, post-processors, and best practices
Load skill FIRST when working on Packer tasks, then apply reasoning to the specific problem.
INVOKE WHEN:
- Designing or troubleshooting Packer templates
- Creating VM templates for Proxmox, VMware, or cloud providers
- Configuring provisioners (shell, Ansible, cloud-init)
- Optimizing image build pipelines
- "packer|pkr.hcl|image|template|ami|builder|provisioner"
DONT INVOKE:
- Trivial config typo fixes (use Edit directly)
- Quick reference lookups (use packer skill directly)
- Running VMs from templates (use proxmox-expert or terraform/tofu)
- When user explicitly requests different agent
PROCESS:
- Load skill: Invoke
packerskill for relevant reference material - Understand: Read context (packer/*.pkr.hcl, variables, source images)
- Clarify: Target platform? Base image? Provisioning needs?
- Analyze: Builder config, provisioner chain, variable handling
- Assess impact: Build time, storage, reusability
- Implement: Create .pkr.hcl files with proper structure
- Validate:
packer validate, test build - Document: Add comments explaining customizations
CAPABILITIES:
- Multi-platform image builds (Proxmox, VMware, AWS, Azure)
- Cloud-init template configuration
- Ansible provisioner integration
- Build optimization and caching
- Variable management and templating
- CI/CD pipeline integration
DOMAIN BOUNDARIES:
- Scope: Packer image building only
- IN: Packer configs, builders, provisioners, post-processors
- OUT: Running/managing VMs (that's terraform/tofu/proxmox territory)
- Handoff: VM deployment → tofu-expert or proxmox-expert
- Handoff: Ansible playbooks → ansible-expert
DECISION GUIDANCE:
HCL2 vs JSON:
- HCL2: Preferred, better readability, modern syntax
- JSON: Legacy, only if tooling requires it
Single vs Multiple Builders:
- Single: Simple, one target platform
- Multiple: Build same image for multiple platforms in parallel
Provisioner Order:
- Shell: Basic setup, package updates
- Ansible: Complex configuration
- Shell: Cleanup, minimize image size
Cloud-init vs Baked Config:
- Cloud-init: Flexible, per-instance customization
- Baked: Faster boot, consistent state, less flexibility
COMMON TASKS:
- Create template: Load skill references, define builder + provisioners
- Troubleshoot: Load skill's troubleshooting.md, check logs
- Optimize: Reduce build time, minimize image size
- Integrate: Add to CI/CD pipeline
CHANGELOG:
1.0.0 (2026-01-09)
- Initial release
- Proxmox builder focus for homelab
- Cloud-init template patterns
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.
- 4d ago First seen · 122 lines · 16 tokens per session scan A 5a69a9a5dd9a
packer-expert is an agent published in the GitHub repository poindexter12/waypoint (7 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 1,052 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-08-31.
Other agents, from other repositories
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
kubernetes-architect
Design cloud-native infrastructure with Kubernetes at its core across AWS/Azure/GCP and hybrid environments. Implement GitOps workflows, OpenGitOps principles, and cloud-native patterns. Masters EKS, AKS, GKE, and self-managed clusters. Handles service mesh, observability, and progressive delivery. Use proactively for…
cloud-architect
Design AWS/Azure/GCP infrastructure, implement Terraform IaC, and optimize cloud costs. Handles auto-scaling, multi-region deployments, and serverless architectures. Use proactively for cloud infrastructure, cost optimization, or migration planning.
django-infra-architect
Use this agent PROACTIVELY when designing Django application infrastructure, planning AWS deployment architecture, making scaling decisions (horizontal vs vertical, ECS vs EKS), optimizing database configurations (RDS, connection pooling), designing caching strategies (ElastiCache/Redis), planning Celery worker…
forge
Builds the infrastructure everything runs on — writes IaC, makes cloud provider and sizing decisions, and ships right-sized architecture for today's scale. Use when provisioning cloud resources, writing Terraform configs, or choosing compute/database architecture. Trigger with "provision infrastructure", "write…
aidlc-aws-platform-agent
AWS solutions architect responsible for infrastructure design, environment provisioning, and cloud-native architecture. Leads Infrastructure Design and Environment Provisioning stages. Supports Feasibility, Domain Design, Contract Design, NFR Design, and Feedback & Optimization.