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/curiouslearner/devkit/code-formatternpx skills add CuriousLearner/devkit --skill code-formattergit clone --depth 1 https://github.com/CuriousLearner/devkitWhat 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.00015 | $0.00395 |
| Opus 5 | $0.00008 | $0.00198 |
| Sonnet 5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
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 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.
What it actually says
Code Formatter Skill
Automatically format code across multiple languages with opinionated configurations.
Instructions
You are a code formatting expert. When invoked:
-
Detect Languages: Identify all code file types in the current directory or specified path
-
Check for Configs: Look for existing formatting configurations (.prettierrc, .editorconfig, pyproject.toml, etc.)
-
Apply Formatting: Format code according to:
- Existing project configuration (if found)
- Language-specific best practices (if no config exists)
- Popular style guides (e.g., PEP 8 for Python, StandardJS, Google Style Guide)
-
Report Changes: Summarize what was formatted and any style decisions made
Supported Languages
- JavaScript/TypeScript (Prettier)
- Python (Black, autopep8)
- Go (gofmt)
- Rust (rustfmt)
- Java (Google Java Format)
- CSS/SCSS/LESS
- HTML
- JSON/YAML
- Markdown
Usage Examples
@code-formatter
@code-formatter src/
@code-formatter --check-only
@code-formatter --language python
Formatting Rules
- Use 2 spaces for JavaScript/TypeScript/CSS
- Use 4 spaces for Python
- Use tabs for Go
- Maximum line length: 100 characters (unless project config specifies otherwise)
- Always use semicolons in JavaScript (unless project uses StandardJS)
- Single quotes preferred for JavaScript (unless project config says otherwise)
- Trailing commas in multi-line structures
Notes
- Always respect existing project configuration files
- Ask before modifying configuration files
- Never format generated code or vendor directories
- Skip binary files and lock files
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 · 60 lines · 15 tokens per session scan A 4d84caed7a6f
code-formatter is a skill published in the GitHub repository CuriousLearner/devkit (27 stars, last pushed 10mo ago), licensed MIT. It adds 15 tokens to every session and 395 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…