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 commands/thelobbi/claude/helm-deploygit clone --depth 1 https://github.com/TheLobbi/claudeWrote 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/commands/thelobbi/claude/helm-deploy)<a href="https://agentmods.dev/commands/thelobbi/claude/helm-deploy"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/helm-deploy.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.00015 | $0.00382 |
| Opus 5 | $0.00008 | $0.00191 |
| Sonnet 5 | $0.00003 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
helm-deploy 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 3d 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
Helm Deployment
Execute Helm deployment operations. Available operations:
Usage
/helm-deploy <operation> [options]
Operations
Deployment
install- Install new Helm releaseupgrade- Upgrade existing releaseupgrade-install- Install or upgrade release
Release Management
status- Get release statushistory- View release historyrollback- Rollback to previous revisionuninstall- Remove release
Debugging
template- Render templates locallylint- Lint chart for issuesdiff- Show diff before upgradetest- Run Helm tests
Values
values-get- Get current release valuesvalues-validate- Validate values file
Examples
# Deploy to development
/helm-deploy upgrade-install --env dev --set image.tag=dev-latest
# Deploy to production with dry-run
/helm-deploy upgrade-install --env prod --dry-run
# Rollback to previous version
/helm-deploy rollback --revision 2
# Show what would change
/helm-deploy diff --env staging
# Get release status
/helm-deploy status --env production
Environments
dev- Development (values-dev.yaml)staging- Staging (values-staging.yaml)prod- Production (values-prod.yaml)
Agent Assignment
This command activates the helm-release-manager agent for execution.
Prerequisites
- kubectl configured with cluster access
- Helm 3.x installed
- Chart located at
deployment/helm/alpha-members/
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.
- 3d ago First seen · 68 lines · 15 tokens per session scan A 3004d1ce71f2
helm-deploy is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed 6d ago), licensed MIT. It adds 15 tokens to every session and 382 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 commands, from other repositories
deploy
Build, test, deploy with staged rollout.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
cf-scaffold-project
Scaffold a Cloudflare project — Worker, Pages, or Worker+D1+R2 starter — with Wrangler config, Terraform skeleton, and GitHub Actions deploy using scoped API tokens.
overview
Unified cost dashboard combining state, plan, actual costs, projected costs, drift, and recommendations.
scan
Scan AWS account for cost optimization.
finops-feedback
Step 5 (Feedback Loop & Celebration) — measure realized against projected savings, compute a labelled Cloud Entropy proxy, close the opportunity, and emit at least one new idea or policy update so the loop actually closes. Applies the double-loop gate. Mutates on the closure path.