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/drag88/claude-dev-framework/coding-standardsnpx skills add drag88/claude-dev-framework --skill coding-standardsgit clone --depth 1 https://github.com/drag88/claude-dev-frameworkWhat 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.00028 | $0.01460 |
| Opus 5 | $0.00014 | $0.00730 |
| Sonnet 5 | $0.00006 | $0.00292 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
coding-standards 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.
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Standards Skill
Enforce consistent code quality principles and patterns across all implementation work.
When to Activate
- During any code implementation task (
/cdf:implement) - When reviewing or refactoring code
- When writing new functions, classes, or modules
- When the user requests coding guidance or best practices
Pattern Index
Core Principles
| Principle | Rule |
|---|---|
| Readability First | Optimize for human understanding over cleverness |
| KISS | Simplest solution that works is usually best |
| DRY | Extract repeated logic, avoid premature abstraction |
| YAGNI | Don't build for hypothetical future requirements |
Readability First
// BAD: Clever but unclear
const r = a.filter(x => x.t === 'p' && x.s > 0).map(x => x.v);
// GOOD: Clear and intentional
const activeProducts = items
.filter(item => item.type === 'product' && item.stock > 0)
.map(item => item.value);
KISS (Keep It Simple, Stupid)
// BAD: Over-engineered
class UserNameFormatter {
private strategies = new Map<string, FormatterStrategy>();
constructor() {
this.registerStrategy('default', new DefaultStrategy());
// ... 50 more lines
}
}
// GOOD: Simple function
function formatUserName(user: User): string {
return `${user.firstName} ${user.lastName}`.trim();
}
DRY (Don't Repeat Yourself)
// BAD: Duplicated logic
function validateEmail(email: string) {
return email.includes('@') && email.includes('.');
}
function validateUserEmail(user: User) {
return user.email.includes('@') && user.email.includes('.');
}
// GOOD: Single source of truth
function isValidEmail(email: string): boolean {
return email.includes('@') && email.includes('.');
}
function validateUserEmail(user: User): boolean {
return isValidEmail(user.email);
}
YAGNI (You Aren't Gonna Need It)
// BAD: Building for imaginary requirements
interface User {
id: string;
name: string;
futureField1?: string; // "We might need this"
extensionData?: Record<string, unknown>; // "For flexibility"
}
// GOOD: Build what you need now
interface User {
id: string;
name: string;
}
What ships with it
3 files 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.
- yesterday First seen · 225 lines · 28 tokens per session scan A a750ed3cb493
coding-standards is a skill published in the GitHub repository drag88/claude-dev-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 1,460 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-31.
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…