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/fix-log/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/fix-log)<a href="https://agentmods.dev/skills/cloudposse/atmos/fix-log"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/fix-log/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/fix-log"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/fix-log.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.00700 |
| Opus 5.5 | $0.00020 | $0.00280 |
| Sonnet 5.5 | $0.00010 | $0.00140 |
| Haiku 4.5 | $0.00005 | $0.00070 |
Grade A, and why
fix-log 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 2d 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.
Fix Documentation
Every implemented fix must leave a short Markdown record in docs/fixes/.
docs/fixes/ already contains 90+ pre-existing records in an older, inconsistent format (some with a
# Fix: <title> heading, some without; some with a **Date:** line, some without; and 25+ different ad hoc
## section names across the set — ## Problem, ## Root Cause, ## Tests, ## Related, etc.). Do not
migrate those — they stay as-is. All new records use the merged format below, which keeps the old
convention's most useful, scannable elements (the # Fix: heading, the explicit **Date:** line) and adopts
a single, consistent five-section structure instead of ad hoc headers.
Workflow
- Before final ready status, create or update
docs/fixes/YYYY-MM-DD-<slug>.md. - Use the current local date for
YYYY-MM-DD. - Use a lowercase slug with letters, numbers, and hyphens.
- Record what changed, why it changed, validation that actually ran, and follow-ups.
- Do not invent validation. If a check was skipped or blocked, say why.
- Follow
CLAUDE.md's Follow-up Tracking (MANDATORY) rule: never create GitHub issues for an implementation that has not merged intomain. Fix required work in the active PR or stack and keep remaining tasks in its PRD or task list. The Follow-ups section may link to that document; an issue number is not required. Only for already-merged features, track genuinely deferred work in a GitHub issue and link it by number.
Required Document Shape
# Fix: <Title>
**Date:** YYYY-MM-DD
## Summary
## Context
## Changes
## Validation
## Follow-ups
<Title>is a short human-readable description of the fix (inline code spans are fine, e.g.# Fix: `describe affected` now checks `source` and `provision` sections).**Date:**restates the filename's date for at-a-glance scanning; keep it in sync with the filename.- Use
None.inFollow-upsonly when no follow-up is known.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed · +1 lines d2c9c07a00fb
- 1mo ago First seen · 67 lines · 50 tokens per session scan A 2d2fd8ad44fc
fix-log is a skill published in the GitHub repository cloudposse/atmos (1,403 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 700 once invoked, about $0.0002 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
clum-mcp
A procedure for using clum, a remote Linux operations platform that runs commands through a secure proxy rather than direct SSH. It also describes how to inspect systems, investigate failures, compare solutions, and review incidents.
claw-admin
Claw system administration: service management, IM connections, logs, cron, and workspace diagnostics. Use when the user asks to manage claw services, connect/disconnect IM platforms, view logs, or perform system-wide operations.
optimize
Review code for efficiency and performance. Triggered by "/optimize" when user wants to identify bottlenecks or improve performance.
gke-basics
Trigger: Use when working with Google Kubernetes Engine basics — cluster setup, node pools, workloads, networking, and storage fundamentals.
doris-debug-cloud
Use for Doris storage-compute separation (cloud mode) issues: meta-service latency, cache miss storms, object store throughput, and shared-nothing config conflicts in compute groups.
huaweicloud-troubleshooting
Troubleshoot Huawei Cloud CLI, API, SDK, deployment, permission, region, quota, endpoint, and resource errors. Use when commands fail, APIs return errors, resources are missing, or the user needs a structured diagnosis.