code-hygiene

A focused code-review check for architectural smells that linting, tests, and coverage do not reliably find. It compares changed code with the repository's own architectural rules.

In plain words
What is it for?
Use it to review the files changed in a patch and report structural design problems for a human or later planning pass to decide.
Why use it?
It can reveal duplicated abstractions, misplaced business logic, or code that appears to validate a request without carrying it out.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/cloudposse/atmos/code-hygiene
Any agent
npx skills add cloudposse/atmos --skill code-hygiene
Clone the repo
git clone --depth 1 https://github.com/cloudposse/atmos

Made for: Claude Code, Codex.

Per session 225 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,777 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00225 $0.02777
Opus 5 $0.00112 $0.01388
Sonnet 5 $0.00045 $0.00555
Haiku 4.5 $0.00022 $0.00278

Measured yesterday against content hash 113e5c038ff6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-hygiene 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 yesterday.

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.

.claude/skills/code-hygiene/SKILL.md · 167 lines

How it starts

The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Hygiene

A narrow, calibrated review pass — not a general bug hunt. lint catches syntactic violations, test-coverage catches untested lines, and a normal correctness-focused review catches bugs — none of those structurally catch an abstraction that got duplicated instead of reused, a feature that validates but silently does nothing, or a comment that admits a gap nobody closed. This skill's job is specifically the class of smell that only shows up when you read code against this repo's own architectural mandates (CLAUDE.md) and ask "does this actually do what it claims to," not just "does this compile and pass its own tests."

This skill reports; it does not redesign. A real architectural smell usually needs a design decision, not a mechanical patch — report it clearly enough that a human (or a follow-up planning pass) can make that call. See "Auto-fix policy" below for the one narrow exception.

Scope: patch-aware by default

Default to the same scoping convention as lint/test-coverage: review only the files/packages touched by git diff origin/main...HEAD --name-only (or the currently open PR's diff). This never goes hunting through the other 340+ packages the current patch didn't touch. Unlike lint (which wraps a real atmos fix lint command with an actual --new-from-rev flag), this skill has no underlying CLI command — there's no literal flag to pass, only the phrasing below.

Full-repo mode (explicit only)

Only when a human explicitly asks for a full sweep (e.g. "audit the whole repo", "full code hygiene sweep" — never inferred, never run from fix-all's automated cycle). A whole-repo pass is expensive and belongs in an on-demand invocation, not an hourly loop.

Dedup: skip a re-run against an unchanged diff

Before reviewing, hash git diff origin/main...HEAD (the diff content itself — this skill's dedup key is "has the patch changed," not an external event set) and compare against .claude/state/code-hygiene/<branch-slug>.json's last-recorded hash. The .claude/state/<name>/ <branch-slug>.json file shape is borrowed from .claude/hooks/security-remediate-trigger.sh — the one existing precedent for this pattern in this repo, not an established multi-skill convention — adapted here to hash the diff instead of a set of alert IDs, since what's being deduped against is different (a review cycle re-running on unchanged code, not a repeated external notification). If the hash matches, skip re-reviewing and reuse the cached findings array from that state file — report it as a one-line no-op citing the cached result count, don't burn tokens re-deriving the same answer from an unchanged patch. If the hash differs (or no state file exists yet), do the full review below, then write {hash, findings, ts} back to the state file after reporting.

Read the full file on GitHub · 167 lines

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.

  1. yesterday First seen · 167 lines · 225 tokens per session scan A 113e5c038ff6

Subscribe to this mod's changes

code-hygiene is a skill published in the GitHub repository cloudposse/atmos (1,365 stars, last pushed today), licensed Apache-2.0. It adds 225 tokens to every session and 2,777 once invoked, about $0.0011 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.

Related

Other skills, from other repositories

x-cmd-advise

Skill "x-cmd-advise" from x-cmd/x-cmd, covering x-cmd advise writing guide, core principles, field quick reference, subcommands at root level and writing priority.

x-cmd/x-cmd · 0 tokens

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.

x-cmd/x-cmd · 48 tokens

x-nets

Enhanced netstat module with cached data and structured output. View network connections, routing tables, and interface statistics in interactive or TSV/CSV formats. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 69 tokens

x-arp

Display ARP cache table with MAC vendor lookup and suspicious entry detection. Supports CSV, TSV, and TUI output. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 64 tokens

x-mankier

Search and browse man pages from ManKier.com. Command line interface for ManKier man page repository. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 62 tokens

x-osv

CLI for Google OSV database. Query vulnerabilities for packages, scan local projects for vulnerable dependencies. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill). Required Tool: Install osv-scanner for project scanning (see https://github.com/google/osv-scanner).

x-cmd/x-cmd · 72 tokens