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/benshapyro/cadre-devkit-claude/code-formatternpx skills add benshapyro/cadre-devkit-claude --skill code-formattergit clone --depth 1 https://github.com/benshapyro/cadre-devkit-claudeWrote 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/benshapyro/cadre-devkit-claude/code-formatter)<a href="https://agentmods.dev/skills/benshapyro/cadre-devkit-claude/code-formatter"><img src="https://agentmods.dev/badge/skills/benshapyro/cadre-devkit-claude/code-formatter.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00061 | $0.01233 |
| Opus 5 | $0.00030 | $0.00616 |
| Sonnet 5 | $0.00012 | $0.00247 |
| Haiku 4.5 | $0.00006 | $0.00123 |
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 3d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Formatter Skill
Apply consistent code formatting and style according to established guidelines.
Formatting Standards
File Naming
- All files:
lowercase_with_underscores - Examples:
user_service.py,api_client.ts,data_helper.js
Variable Naming
- Variables/Functions:
camelCase - Classes/Components:
PascalCase - Constants:
UPPER_CASE_SNAKE_CASE
// Good
const userName = 'John';
const API_KEY = 'secret';
class UserService {}
function getUserData() {}
// Bad
const UserName = 'John';
const api_key = 'secret';
class userService {}
function get_user_data() {}
Code Style
Line Length
- Maximum 100 characters per line
- Break long lines logically at operators or delimiters
Commas
- Use trailing commas for multi-line objects and arrays
// Good
const config = {
host: 'localhost',
port: 3000,
timeout: 5000, // trailing comma
};
const items = [
'first',
'second',
'third', // trailing comma
];
// Bad
const config = {
host: 'localhost',
port: 3000,
timeout: 5000 // missing trailing comma
};
Imports
- Use explicit imports (no wildcard
*) - ES Modules only (no
require) - Group imports: external libraries first, then internal modules
// Good
import { useState, useEffect } from 'react';
import { fetchUser } from '../api/users';
// Bad
import * from 'react';
const users = require('../api/users');
Async/Await
- Prefer
async/awaitover.then()chains
// Good
async function fetchData() {
const response = await apiClient.get('/data');
return response.data;
}
// Bad
function fetchData() {
return apiClient.get('/data').then(res => res.data);
}
TypeScript Standards
- Enable strict mode
- Avoid
anytype (useunknownif type is truly unknown) - Define interfaces for object shapes
- Use type annotations for function parameters and returns
// Good
interface User {
id: number;
name: string;
email: string;
}
async function getUser(id: number): Promise<User> {
const response = await fetch(`/api/users/${id}`);
return response.json();
}
// Bad
async function getUser(id) {
const response = await fetch(`/api/users/${id}`);
return response.json();
}
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.
- 3d ago First seen · 230 lines · 61 tokens per session scan A d7fe4c051ed5
code-formatter is a skill published in the GitHub repository benshapyro/cadre-devkit-claude (9 stars, last pushed 9mo ago), licensed MIT. It adds 61 tokens to every session and 1,233 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…