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/webdevtodayjason/titanium-plugins/code-quality-standardsnpx skills add webdevtodayjason/titanium-plugins --skill code-quality-standardsgit clone --depth 1 https://github.com/webdevtodayjason/titanium-pluginsWhat 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.00048 | $0.05471 |
| Opus 5 | $0.00024 | $0.02736 |
| Sonnet 5 | $0.00010 | $0.01094 |
| Haiku 4.5 | $0.00005 | $0.00547 |
Grade A, and why
code-quality-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 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.
How it starts
The opening of the file, as written. The whole thing — 1,075 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Standards
This skill provides comprehensive guidance for writing clean, maintainable, and high-quality code.
SOLID Principles
S - Single Responsibility Principle
Definition: A class should have only one reason to change.
// ❌ BAD - Multiple responsibilities
class UserManager {
createUser(data: UserData) {
// Validation logic
if (!data.email.includes('@')) throw new Error('Invalid email');
// Database logic
const user = database.insert('users', data);
// Email logic
emailService.send(data.email, 'Welcome!');
// Logging logic
logger.info(`User created: ${data.email}`);
return user;
}
}
// ✅ GOOD - Single responsibility per class
class UserValidator {
validate(data: UserData): void {
if (!data.email.includes('@')) {
throw new Error('Invalid email');
}
}
}
class UserRepository {
create(data: UserData): User {
return database.insert('users', data);
}
}
class UserNotificationService {
sendWelcomeEmail(email: string): void {
emailService.send(email, 'Welcome!');
}
}
class UserService {
constructor(
private validator: UserValidator,
private repository: UserRepository,
private notificationService: UserNotificationService,
private logger: Logger
) {}
async createUser(data: UserData): Promise<User> {
this.validator.validate(data);
const user = await this.repository.create(data);
await this.notificationService.sendWelcomeEmail(user.email);
this.logger.info(`User created: ${user.email}`);
return user;
}
}
O - Open/Closed Principle
Definition: Classes should be open for extension but closed for modification.
// ❌ BAD - Must modify class to add new payment methods
class PaymentProcessor {
process(type: string, amount: number) {
if (type === 'credit_card') {
// Process credit card
} else if (type === 'paypal') {
// Process PayPal
} else if (type === 'bitcoin') {
// Process Bitcoin
}
}
}
// ✅ GOOD - Can extend without modifying
interface PaymentMethod {
process(amount: number): Promise<PaymentResult>;
}
class CreditCardPayment implements PaymentMethod {
async process(amount: number): Promise<PaymentResult> {
// Process credit card
return { success: true };
}
}
class PayPalPayment implements PaymentMethod {
async process(amount: number): Promise<PaymentResult> {
// Process PayPal
return { success: true };
}
}
class PaymentProcessor {
async process(method: PaymentMethod, amount: number): Promise<PaymentResult> {
return await method.process(amount);
}
}
// Add new payment method without modifying existing code
class BitcoinPayment implements PaymentMethod {
async process(amount: number): Promise<PaymentResult> {
// Process Bitcoin
return { success: true };
}
}
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 · 1,075 lines · 48 tokens per session scan A dc82e6dd41c3
code-quality-standards is a skill published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 7mo ago), licensed MIT. It adds 48 tokens to every session and 5,471 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-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…