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/whitebeardit/.cursor/skill-code-qualitynpx skills add whitebeardit/.cursor --skill skill-code-qualitygit clone --depth 1 https://github.com/whitebeardit/.cursorWhat 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.00039 | $0.01519 |
| Opus 5 | $0.00019 | $0.00759 |
| Sonnet 5 | $0.00008 | $0.00304 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
code-quality 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Best Practices
This skill provides code quality principles, design patterns, and practices for writing maintainable, clean code across multiple programming languages.
SOLID Principles
S - Single Responsibility Principle
A class/function should have only one reason to change.
// ❌ Bad: Multiple responsibilities
class User {
save() { /* database logic */ }
sendEmail() { /* email logic */ }
validate() { /* validation logic */ }
}
// ✅ Good: Single responsibility
class User {
validate() { /* validation only */ }
}
class UserRepository {
save(user: User) { /* database logic */ }
}
class EmailService {
sendEmail(user: User) { /* email logic */ }
}
O - Open/Closed Principle
Open for extension, closed for modification.
// ✅ Good: Extensible without modification
interface PaymentProcessor {
process(amount: number): Promise<PaymentResult>;
}
class CreditCardProcessor implements PaymentProcessor {
async process(amount: number) { /* credit card logic */ }
}
class PayPalProcessor implements PaymentProcessor {
async process(amount: number) { /* PayPal logic */ }
}
L - Liskov Substitution Principle
Subtypes must be substitutable for their base types.
// ✅ Good: Subtypes can replace base types
class Bird {
move() { /* generic movement */ }
}
class Sparrow extends Bird {
move() { this.fly(); }
}
class Penguin extends Bird {
move() { this.walk(); }
}
I - Interface Segregation Principle
Clients shouldn't depend on interfaces they don't use.
// ❌ Bad: Fat interface
interface Worker {
work(): void;
eat(): void;
sleep(): void;
}
// ✅ Good: Segregated interfaces
interface Workable {
work(): void;
}
interface Eatable {
eat(): void;
}
interface Sleepable {
sleep(): void;
}
D - Dependency Inversion Principle
Depend on abstractions, not concretions.
// ❌ Bad: Depends on concrete class
class OrderService {
private emailService = new EmailService();
}
// ✅ Good: Depends on abstraction
class OrderService {
constructor(private emailService: IEmailService) {}
}
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 · 311 lines · 39 tokens per session scan A 75c02ea39922
code-quality is a skill published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 1,519 once invoked, about $0.0002 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.
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…