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 skills/cloudposse/atmos/fix-lognpx skills add cloudposse/atmos --skill fix-loggit clone --depth 1 https://github.com/cloudposse/atmosWhat 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.00050 | $0.00693 |
| Opus 5 | $0.00025 | $0.00347 |
| Sonnet 5 | $0.00010 | $0.00139 |
| Haiku 4.5 | $0.00005 | $0.00069 |
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 — 67 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.
- If the fix leaves any follow-up work (anything under Follow-ups other than
None.), it must satisfyCLAUDE.md's Follow-up Tracking (MANDATORY) section: open a GitHub issue and link it by number (e.g.#1234) in the Follow-ups section. A Follow-ups entry like "a follow-up will..." with no issue number is incomplete — the work will never be tracked.
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.
Validation
After creating or updating fix docs, run:
bash .claude/skills/fix-log/scripts/validate-fix-doc.sh docs/fixes/*.md
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 First seen · 67 lines · 50 tokens per session scan A 2d2fd8ad44fc
fix-log is a skill published in the GitHub repository cloudposse/atmos (1,367 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 693 once invoked, about $0.0003 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-30.
Other skills, from other repositories
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
trigger-authoring-tasks
Covers writing backend Trigger.dev tasks with @trigger.dev/sdk: defining task() and schemaTask(), the run function and its ctx, retries, waits, queues and concurrency, idempotency keys, run metadata, logging, triggering other tasks (and the Result shape), scheduled/cron tasks, and the essentials of trigger.config.ts.…
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
dstack-presets
Create and manage dstack presets: a toolkit that streamlines model inference optimization with agents, and a portable preset format. Use together with the dstack skill, and only when the user explicitly asks to create a preset or manage existing presets, not for deploying or serving a model.