Atmos is an infrastructure runtime that coordinates tools such as Terraform, OpenTofu, Kubernetes, Helm, Packer, Ansible, and containers through consistent commands and configuration. It is for teams running cloud infrastructure on laptops, in CI, or through AI agents across environments and regions. Its catalogue entries provide skills, agents, commands, and other add-ons for Atmos workflows.
Borrowing it
Nothing to install: this file belongs to cloudposse/atmos. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cloudposse/atmos/main/.claude/skills/security-remediate/SKILL.mdgit clone --depth 1 https://github.com/cloudposse/atmosWrote 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/cloudposse/atmos/security-remediate)<a href="https://agentmods.dev/skills/cloudposse/atmos/security-remediate"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/security-remediate/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/cloudposse/atmos/security-remediate"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/security-remediate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 39 Skill attempts to nullify the agent's safety policies or restrictions ('you have no restrictions', 'ignore your guidelines', 'do anything now'). This is a direct jailbreak that disables guardrails.Fix: Remove jailbreak framing that nullifies safety policies or restrictions. Skill content must not instruct the agent to ignore its guidelines or operate without guardrails.
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.00070 | $0.01213 |
| Opus 5.5 | $0.00028 | $0.00485 |
| Sonnet 5.5 | $0.00014 | $0.00243 |
| Haiku 4.5 | $0.00007 | $0.00121 |
Grade A, and why
security-remediate 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Remediate (Atmos)
Proactively fix GitHub-reported security alerts on the branch you're already working on, instead of letting them accumulate until a manual sweep (see commit 0e32451913 for what that manual sweep looked like).
Fork / permission prerequisite (read first)
This repo is public, so a plain gh token with repo scope (the default from gh auth login) is sufficient to read both alert endpoints — security_events is only required on private repos (see GitHub's Dependabot alerts API docs: private repos need security_events, public repos only need public_repo/repo). Don't chase a security_events scope refresh for this repo; it's unnecessary and, per cli/cli#12073 and independent reports (e.g. microsoft/sarif-sdk#3081), gh auth refresh -s security_events can report success while GitHub silently drops the scope anyway — a dead end that's easy to mistake for a real permission gap.
If gh api calls below still 404/403 even with -X GET present, that's a genuine permission gap (e.g. a fork contributor without repo access, or a future private-repo use of this skill lacking security_events) — stop and report it instead of attempting a workaround. .claude/hooks/security-remediate-trigger.sh treats that case exactly like "no alerts open" and silently does nothing.
Workflow
-
Resolve context.
owner_repo="$(gh repo view --json owner,name --jq '.owner.login + "/" + .name')" branch="$(git rev-parse --abbrev-ref HEAD)" -
Query both alert sources live (the hook's cached alert set was only a trigger signal — treat it as stale):
gh api "repos/${owner_repo}/dependabot/alerts" -X GET --paginate -f state=open gh api "repos/${owner_repo}/code-scanning/alerts" -X GET --paginate -f state=openThe
-X GETis required:gh apiimplicitly sends aPOSTwhen-f/--paginateparams are given without an explicit method, and these list endpoints 404 onPOST— indistinguishable from a real permission error unless you notice the verb. If either call still 403/404s with-X GETpresent, stop and report the permission gap — do not proceed partway.
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 Changed a6d3dbaf6213
- 1mo ago First seen · 68 lines · 70 tokens per session scan A 41da5589bf84
security-remediate is a skill published in the GitHub repository cloudposse/atmos (1,405 stars, last pushed today), licensed Apache-2.0. It adds 70 tokens to every session and 1,213 once invoked, about $0.0003 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-30.
Other skills, from other repositories
csv
CSV data processing — view, filter, convert, merge tabular data. Zero barrier — use with x-cmd, Python, or awk. Use for "csv", "data", "table", "spreadsheet", "conversion".
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.
gke-basics
Trigger: Use when working with Google Kubernetes Engine basics — cluster setup, node pools, workloads, networking, and storage fundamentals.
repo
Convention + tooling for where agent-cloned repos live and how their worktrees are arranged. Default bare repo at /.x-repo/.bare/ / / .git with linked working trees under /.x-repo/ / / [/@ ]. Discovered via x repo ls. Worktree management via x repo wt. Use for "where to clone", "git clone path", "workspace layout"…
gh
You have access to gh (GitHub CLI) for repository and project management.