code-quality-principles

code-quality-principles is a skill for Claude Code from athola/claude-night-market. It costs 38 tokens per session (2,028 once invoked), scanned A, original, MIT.

A set of guidelines for keeping software simple, readable, and easier to maintain. It covers KISS, meaning “keep it simple,” YAGNI, meaning “do not build unnecessary things,” and SOLID design principles.

In plain words
What is it for?
It supports refactoring and code review by suggesting simpler structures and language-specific examples.
Why use it?
It helps prevent over-engineered code, needless abstractions, and clever shortcuts that make future changes harder.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the conserve plugin — 15 skills, 6 commands, 5 agents shipped together

Good fit It supports refactoring and code review by suggesting simpler structures and language-specific examples.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/athola/claude-night-market/code-quality-principles
Install

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.

Any agent
npx skills add athola/claude-night-market --skill code-quality-principles
Clone the repo
git clone --depth 1 https://github.com/athola/claude-night-market

Made for: Claude Code.

Or install conserve, the plugin that ships this one along with the rest of its 15 skills, 6 commands, 5 agents.

Wrote 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.

agentmods badge for code-quality-principles

README.md
[![agentmods](https://agentmods.dev/badge/skills/athola/claude-night-market/code-quality-principles/github.svg)](https://agentmods.dev/skills/athola/claude-night-market/code-quality-principles)
Your own site
<a href="https://agentmods.dev/skills/athola/claude-night-market/code-quality-principles"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/code-quality-principles/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for code-quality-principles

Your own site · 80×15
<a href="https://agentmods.dev/skills/athola/claude-night-market/code-quality-principles"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/code-quality-principles.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,028 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.02028
Opus 5 $0.00019 $0.01014
Sonnet 5 $0.00008 $0.00406
Haiku 4.5 $0.00004 $0.00203

Measured 5d ago against content hash 7b0e5e72a1c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

code-quality-principles 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 5d 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.

plugins/conserve/skills/code-quality-principles/SKILL.md · 320 lines

How it starts

The opening of the file, as written. The whole thing — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Quality Principles

Guidance on KISS, YAGNI, and SOLID principles with language-specific examples.

When To Use

  • Improving code readability and maintainability
  • Applying SOLID, KISS, YAGNI principles during refactoring

When NOT To Use

  • Throwaway scripts or one-time data migrations
  • Performance-critical code where readability trades are justified

KISS (Keep It Simple, Stupid)

Principle: Avoid unnecessary complexity. Prefer obvious solutions over clever ones.

Guidelines

Prefer Avoid
Simple conditionals Complex regex for simple checks
Explicit code Magic numbers/strings
Standard patterns Clever shortcuts
Direct solutions Over-abstracted layers

Python Example

# Bad: Overly clever one-liner
users = [u for u in (db.get(id) for id in ids) if u and u.active and not u.banned]

# Good: Clear and readable
users = []
for user_id in ids:
    user = db.get(user_id)
    if user and user.active and not user.banned:
        users.append(user)

Rust Example

// Bad: Unnecessary complexity
fn process(data: &[u8]) -> Result<Vec<u8>, Box<dyn std::error::Error>> {
    data.iter()
        .map(|&b| b.checked_add(1).ok_or("overflow"))
        .collect::<Result<Vec<_>, _>>()
        .map_err(|e| e.into())
}

// Good: Simple and clear
fn process(data: &[u8]) -> Result<Vec<u8>, &'static str> {
    let mut result = Vec::with_capacity(data.len());
    for &byte in data {
        result.push(byte.checked_add(1).ok_or("overflow")?);
    }
    Ok(result)
}

YAGNI (You Aren't Gonna Need It)

Principle: Don't implement features until they are actually needed.

Guidelines

Do Don't
Solve current problem Build for hypothetical futures
Add when 3rd use case appears Create abstractions for 1 use case
Delete dead code Keep "just in case" code
Minimal viable solution Premature optimization

Python Example

# Bad: Premature abstraction for one use case
class AbstractDataProcessor:
    def process(self, data): ...
    def validate(self, data): ...
    def transform(self, data): ...


class CSVProcessor(AbstractDataProcessor):
    def process(self, data):
        return self.transform(self.validate(data))


# Good: Simple function until more cases appear
def process_csv(data: list[str]) -> list[dict]:
    return [parse_row(row) for row in data if row.strip()]

Read the full file on GitHub · 320 lines

Changes

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.

  1. 5d ago First seen · 320 lines · 38 tokens per session scan A 7b0e5e72a1c5

Subscribe to this mod's changes

code-quality-principles is a skill published in the GitHub repository athola/claude-night-market (336 stars, last pushed 3d ago), licensed MIT. It adds 38 tokens to every session and 2,028 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-09-03.

Related

Other skills, from other repositories

microservices-architecture

Guides service boundary analysis, communication pattern selection, data consistency design, API contract strategy, and resilience checklist for microservices systems. Complements the microservices fragment. Invoked when the user asks to design a microservices system, split a monolith, or review service boundaries.

soulcodex/agentic · 61 tokens

relational-database-design

Designs or reviews a relational database schema for a given domain. Covers table structure, normalization, indexes, constraints, and migration strategy. Invoked when the user asks to design a schema, review a database structure, or optimize a data model.

soulcodex/agentic · 55 tokens

river-review-architecture

An architecture-review guide that checks whether software design decisions, system boundaries, and data models fit together consistently. An architecture review examines the structure and dependencies of a system.

s977043/river-review · 53 tokens

Architecture Boundaries & Dependencies

Ensure architecture/design docs define clear boundaries, ownership, dependency direction, and change impact to avoid tight coupling.

s977043/river-review · 27 tokens

Architecture Diagrams Readiness

Ensure architecture diagrams are readable, consistent with text, and clear on scope, boundaries, and data flow.

s977043/river-review · 27 tokens

Architecture Traceability & Consistency

Ensure design changes stay consistent across ADRs, diagrams, and specs; decisions are traceable; and drift is explicitly managed.

s977043/river-review · 32 tokens