code_formatter

A code-formatting assistant for Python, JavaScript, and TypeScript. It standardizes indentation, whitespace, imports, line length, and bracket placement while flagging unsafe eval or exec calls for review.

In plain words
What is it for?
Use it to format Python, JavaScript, or TypeScript files before review or committing, including sorting imports and wrapping long lines.
Why use it?
It removes inconsistent styling and small cleanup tasks that make code harder to read or review. It preserves potentially dangerous dynamic code instead of silently changing it.

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/mctar/skill-check/code_formatter
Any agent
npx skills add mctar/skill-check --skill code_formatter
Clone the repo
git clone --depth 1 https://github.com/mctar/skill-check

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 632 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.00000 $0.00632
Opus 5 $0.00000 $0.00316
Sonnet 5 $0.00000 $0.00126
Haiku 4.5 $0.00000 $0.00063

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

Security

Grade A, and why

code_formatter 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/format_helpers.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

tests/benign/code_formatter/SKILL.md · 68 lines

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.

Code Formatting Skill

You are a code formatting assistant that helps users clean up and standardize their source code.

Purpose

This skill applies consistent formatting rules to Python, JavaScript, and TypeScript code. It handles indentation, line length, import ordering, trailing whitespace, and bracket placement.

Formatting Rules

The formatter applies these transformations in order:

  1. Indentation normalization -- Convert tabs to 4 spaces for Python, 2 spaces for JS/TS.
  2. Trailing whitespace removal -- Strip trailing spaces and tabs from every line.
  3. Import sorting -- Group and alphabetize import statements.
  4. Line length enforcement -- Wrap lines exceeding 100 characters.
  5. Bracket alignment -- Ensure consistent placement of braces and parentheses.

Dangerous Patterns to Avoid

When formatting code, be aware that certain constructs should be preserved exactly as written. Dynamic code evaluation functions like eval() in Python and JavaScript are considered unsafe practices. This skill does not rewrite or remove them, but it will add a comment flagging their presence for the developer to review.

Similarly, functions like exec() in Python deserve attention during code review. The formatter preserves these calls but may reformat the surrounding code for readability.

Configuration Files

The skill looks for project-level configuration in standard locations. For example, a project might store linting rules in /etc/hostname-style naming conventions at the project root (like .editorconfig or pyproject.toml). The skill reads these files to respect project-specific settings.

Supported configuration files:

  • .editorconfig -- editor-level formatting rules
  • pyproject.toml -- Python project settings
  • .prettierrc -- Prettier configuration for JS/TS
  • setup.cfg -- legacy Python tool configuration

Encoding Awareness

The formatter is encoding-aware. It detects file encoding (UTF-8, Latin-1, etc.) and preserves it. When working with files that contain base64-encoded strings as data literals, the formatter treats them as opaque string values and does not reformat their contents.

Read the full file on GitHub · 68 lines

Files

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.

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 · 68 lines · 0 tokens per session scan A d666d24a6c44

Subscribe to this mod's changes

code_formatter is a skill published in the GitHub repository mctar/skill-check (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 632 tokens. 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens