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 alexmond/jhelm --skill helm-upstreamgit clone --depth 1 https://github.com/alexmond/jhelmWrote 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/alexmond/jhelm/helm-upstream)<a href="https://agentmods.dev/skills/alexmond/jhelm/helm-upstream"><img src="https://agentmods.dev/badge/skills/alexmond/jhelm/helm-upstream/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/alexmond/jhelm/helm-upstream"><img src="https://agentmods.dev/badge/skills/alexmond/jhelm/helm-upstream.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.00016 | $0.00451 |
| Opus 5.5 | $0.00006 | $0.00180 |
| Sonnet 5.5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
helm-upstream 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 1mo 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
Check Upstream Helm Releases
Check the latest Helm releases for closed issues, security fixes, and bug fixes that may be applicable to jhelm.
Steps
- Fetch latest releases (default 4, or
$ARGUMENTSif specified):
gh release list -R helm/helm --limit ${ARGUMENTS:-4}
- Get release notes for each:
gh release view <tag> -R helm/helm
- Fetch closed issues associated with these releases:
gh issue list -R helm/helm --state closed --limit 50 --json number,title,labels,closedAt,body
-
Cross-reference with jhelm — for each issue, determine if it applies:
- Template engine bugs → check jhelm-gotemplate
- Values merging/coalescing → check Engine.java, ValuesLoader.java
- Chart extraction/packaging → check RepoManager.java, ChartLoader.java
- OCI registry → check OciRegistryClient.java
- Security advisories → always check
- CLI/plugin/Kubernetes-specific → usually not applicable
-
Categorize findings:
- APPLICABLE — Action Required: jhelm has the same vulnerability/bug
- APPLICABLE — Verify: jhelm may be affected, needs investigation
- NOT APPLICABLE: jhelm handles this differently or doesn't implement the feature
Report Format
| Issue | Severity | Description | jhelm Status | Action |
|---|---|---|---|---|
| # | Security/Bug/Feature | Summary | Affected/Safe/N/A | Create issue / No action |
For each APPLICABLE finding, suggest whether to create a GitHub issue.
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.
- 1mo ago First seen · 49 lines · 16 tokens per session scan A 4948d130a347
helm-upstream is a skill published in the GitHub repository alexmond/jhelm (7 stars, last pushed 3d ago), licensed Apache-2.0. It adds 16 tokens to every session and 451 once invoked, about $0.0001 per session on Opus 5.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
azure-upgrade
Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code. WHEN: upgrade Consumption to Flex Consumption, upgrade Azure Functions plan, change hosting plan, function app SKU, migrate App Service to Container Apps, modernize legacy Azure Java SDKs…
securing-helm-chart-deployments
Secure Helm chart deployments by validating chart integrity, scanning templates for misconfigurations, and enforcing security contexts in Kubernetes releases.
configuring-airflow-language-sdks
Configures Airflow to run language SDK tasks (Java, Go, and future native SDKs) — register a coordinator, map a queue to it, ensure the runtime/artifact on workers, and tune coordinator options. Use when the user wants Airflow to route a queue to a native-language coordinator, asks about the [sdk]…
nvca-self-managed-install
Install or validate the NVCA Operator chart against a self-managed NVCF control plane from the native monorepo. Use when the control plane comes from deploy/stacks/self-managed and NVCA must be installed with stack-derived image repository settings.
java
Use when writing, reviewing or refactoring modern Java (21+, 25 LTS) — records and sealed interfaces as algebraic data types, exhaustive pattern-matching switch over instanceof ladders, virtual-thread concurrency, structured concurrency and ScopedValue replacing ThreadLocal, Stream and Optional pipelines…
zhihu-search
A search skill for finding content on Zhihu, a Chinese question-and-answer and article platform, through its search API.