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 abdullahkhawer/devops-skills --skill create-terraform-helm-upgrade-plangit clone --depth 1 https://github.com/abdullahkhawer/devops-skillsWrote 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/abdullahkhawer/devops-skills/create-terraform-helm-upgrade-plan)<a href="https://agentmods.dev/skills/abdullahkhawer/devops-skills/create-terraform-helm-upgrade-plan"><img src="https://agentmods.dev/badge/skills/abdullahkhawer/devops-skills/create-terraform-helm-upgrade-plan/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/abdullahkhawer/devops-skills/create-terraform-helm-upgrade-plan"><img src="https://agentmods.dev/badge/skills/abdullahkhawer/devops-skills/create-terraform-helm-upgrade-plan.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.00037 | $0.00995 |
| Opus 5 | $0.00018 | $0.00498 |
| Sonnet 5 | $0.00007 | $0.00199 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
create-terraform-helm-upgrade-plan 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 10d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Terraform Helm Upgrade Plan Skill
Run this skill when asked to analyse a Helm chart upgrade for a Terraform-managed Helm release, or to create an upgrade plan.
Step 1 — Locate the Helm release in Terraform code
Scan the current working directory recursively for Terraform files that define a helm_release resource:
grep -r "helm_release" . --include="*.tf" -l
Read the matching files and extract:
- Helm chart name (the
chartargument) - Helm repository URL (the
repositoryargument) - Any
setblocks that override default values
If no helm_release resource is found, report this and ask the user to confirm the correct directory.
Step 2 — Ask for versions
Ask the user:
1. Current Helm chart version (the version currently deployed)?
2. Desired Helm chart version (the version you want to upgrade to)?
Do not attempt to infer versions from the Terraform code or any VERSION files — always ask.
Step 3 — Find the chart's source repository
Using the repository URL and chart name from Step 1, locate the chart's GitHub.com (or GitLab.com) source repository. Search the web if needed:
<chart-name> helm chart github.com site:github.com
Identify the correct tags for the current and desired versions (e.g. chart-4.12.3 and chart-4.13.1, or just the version numbers, depending on the project's tagging convention).
Step 4 — Compare chart versions
Fetch the diff between the two version tags. The comparison URL typically follows this pattern:
https://github.com/<org>/<repo>/compare/<current-tag>...<desired-tag>.diff
Fetch this URL to retrieve the full diff. If it is unavailable on GitHub.com, search GitLab.com.
Focus on changes in:
templates/— all template filesvalues.yaml— default valuesChart.yaml— chart metadata and dependencies
Step 5 — Search for breaking changes
Search the web for breaking changes between the two versions:
<chart-name> helm chart upgrade <current-version> to <desired-version> breaking 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.
- 10d ago First seen · 145 lines · 37 tokens per session scan A fbad37711ffa
create-terraform-helm-upgrade-plan is a skill published in the GitHub repository abdullahkhawer/devops-skills (7 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 995 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-08-31.
Other skills, from other repositories
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
docs-manage
Manage the Grounded Docs MCP Server documentation index. Covers scraping and indexing documentation from URLs or local files, refreshing existing indexes with changed content, and removing libraries from the index. Use when you need to add, update, or delete indexed documentation.
ecspresso
ECS deployment tool - deploy, manage, and troubleshoot ECS services.
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
ultralytics-platform
This skill should be used when user asks to "upload my model to Ultralytics Platform", "push this run to the platform", "upload a dataset to platform", "download a dataset from platform", "search platform datasets", "start cloud training", "train on platform GPUs", "export a model on platform", "deploy a model…
fetch-url
Fetch a single URL and convert its content to Markdown. Use when you need to read a web page, documentation page, or API reference without indexing it. The content is returned as plain Markdown text on stdout.