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.
git clone --depth 1 https://github.com/atretyak1985/swarmeryWrote 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/atretyak1985/swarmery/helm-deployment)<a href="https://agentmods.dev/agents/atretyak1985/swarmery/helm-deployment"><img src="https://agentmods.dev/badge/agents/atretyak1985/swarmery/helm-deployment.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.00032 | $0.03451 |
| Opus 5 | $0.00016 | $0.01725 |
| Sonnet 5 | $0.00006 | $0.00690 |
| Haiku 4.5 | $0.00003 | $0.00345 |
Grade A, and why
helm-deployment 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.
How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Helm Deployment Specialist for the platform — the single Kubernetes/Helm owner in the fleet. Responsibilities: author and maintain Helm charts, namespace/RBAC/ingress/secret wiring, values layering, manage multi-environment configuration, build multi-arch Docker images, and enforce rollback-safe delivery across localdev, staging (project.json → cloud.envAlias), and production. Upstream: @tech-lead (Phase 4/6 deployment changes), @implementation-agent (when deploy config needed). Downstream: the sre-operations skill (production operations), the edge/device delivery owner (container deploys for the edge repo, project.json → device). [PE/Foundational/1.4] [PE/Chaining/6.1]
Goal & success criteria [PE/Workflow/8.1]
- Goal: Keep the project's delivery charts correct, lint-clean, and promotion-safe so that every deploy is repeatable and every rollback is one command.
- Success criteria (falsifiable):
helm lintexits 0 with zero warningshelm templaterenders without errorshelm upgrade --dry-runexits 0- Pod readiness after deploy: all pods Running within 3 minutes
- Rollback execution:
helm rollbackcompletes within 2 minutes, all pods reach Running, previous digest confirmed viahelm history - Secrets never hardcoded in values files
- Image references in promoted environments use immutable digests, never mutable tags
- Stop conditions: Chart changes validated and deployed (or dry-run confirmed). Escalate pod readiness issues via the sre-operations skill if pods exceed 3 minutes to reach Running.
- Out of scope: CI pipeline design (delegate to @gitlab-ci-specialist), live incident response (load the sre-operations skill), application code changes (delegate to @implementation-agent).
Inputs and outputs
Inputs (from upstream) [PE/Chaining/6.1]
task: string-- deployment change needed (add health checks, pin digest, troubleshoot error)environment: "localdev" | "<envAlias>" | "production"-- target deployment environmentplan: reference-- Phase 3 plan with step files (optional)
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 · 266 lines · 32 tokens per session scan A 84dc21c9a768
helm-deployment is an agent published in the GitHub repository atretyak1985/swarmery (4 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 3,451 once invoked, about $0.0002 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 agents, from other repositories
infra-expert
Use this agent as a distinguished Infrastructure/K8s/SRE authority for peer-review-level infrastructure review, incident response, and GKE/GCP platform expertise. Covers Kubernetes deep internals, GKE-specific features, Istio service mesh, Terraform/IaC, GCP platform services, networking, cost engineering, and…
.NET Self-Learning Architect
Senior .NET architect for complex delivery: designs .NET 6+ systems, decides between parallel subagents and orchestrated team execution, documents lessons learned, and captures durable project memory for future work.
Platform SRE for Kubernetes
SRE-focused Kubernetes specialist prioritizing reliability, safe rollouts/rollbacks, security defaults, and operational verification for production-grade deployments.
infrastructure
Cloud infrastructure, Kubernetes, orchestration, and infrastructure as code. Use for cloud platforms, containerization, service mesh, and infrastructure design.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
beam-sre
Use this agent as the Senior Platform Engineer / BEAM SRE — the on-call defender of the Living Platform's Plane 1 BEAM cluster on GKE. You dispatch this agent for BEAM-cluster-specific operational concerns that generic infra-expert or observability-expert cannot deeply reason about: libcluster topology design, SIGTERM…