a-philosophy-of-software-design

a-philosophy-of-software-design is a skill for Claude Code, Codex from ciembor/agent-rules-books. It costs 33 tokens per session (155 once invoked), scanned A, original, MIT.

A set of software design rules for reducing complexity and choosing module boundaries, abstractions, and APIs.

In plain words
What is it for?
Use it when designing modules or APIs, hiding implementation details, reducing cognitive load, or refactoring interfaces.
Why use it?
It helps prevent interfaces that are hard to understand or change by making responsibilities and abstractions clearer.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when designing modules or APIs, hiding implementation details, reducing cognitive load, or refactoring interfaces.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ciembor/agent-rules-books/a-philosophy-of-software-design
About the project

agent-rules-books is a collection of Markdown rules and skills that guide AI coding agents using principles from books on software design, refactoring, architecture, domain-driven design, reliability, and data systems. Developers use the rules with Codex, Cursor, Claude Code, and other compatible agents to shape how they perform coding tasks. The catalogue skills package these rule sets for installation and use by coding agents.

ciembor/agent-rules-books · 2,741 stars · on GitHub · ciembor.github.io

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 ciembor/agent-rules-books --skill a-philosophy-of-software-design
Clone the repo
git clone --depth 1 https://github.com/ciembor/agent-rules-books

Made for: Claude Code, Codex.

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 a-philosophy-of-software-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/ciembor/agent-rules-books/a-philosophy-of-software-design/github.svg)](https://agentmods.dev/skills/ciembor/agent-rules-books/a-philosophy-of-software-design)
Your own site
<a href="https://agentmods.dev/skills/ciembor/agent-rules-books/a-philosophy-of-software-design"><img src="https://agentmods.dev/badge/skills/ciembor/agent-rules-books/a-philosophy-of-software-design/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 a-philosophy-of-software-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/ciembor/agent-rules-books/a-philosophy-of-software-design"><img src="https://agentmods.dev/badge/skills/ciembor/agent-rules-books/a-philosophy-of-software-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 155 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.
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.00033 $0.00155
Opus 5 $0.00016 $0.00077
Sonnet 5 $0.00007 $0.00031
Haiku 4.5 $0.00003 $0.00015

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

Security

Grade A, and why

a-philosophy-of-software-design 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.

a-philosophy-of-software-design/SKILL.md · 12 lines

What it actually says

A Philosophy of Software Design Skill

Use this skill when a task involves module design, API design, information hiding, abstraction depth, cognitive load, or refactoring shallow interfaces.

Before making design or code decisions, read and apply a-philosophy-of-software-design.mini.md. Use a-philosophy-of-software-design.md only as a deeper reference when the mini rules are not enough for the current design tradeoff.

Files

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.

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. 2d ago First seen · 12 lines · 33 tokens per session scan A c34604b6c55d

Subscribe to this mod's changes

a-philosophy-of-software-design is a skill published in the GitHub repository ciembor/agent-rules-books (2,741 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 155 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-09.

Related

Other skills, from other repositories

software-code-refactoring

Improve production code quality while preserving all existing test behavior. Commonly used for the Refactor phase of TDD red-green-refactor, but applicable to any codebase with tests. Use when production code works but needs cleanup — reducing duplication, improving naming, simplifying complexity, aligning with…

stencila/stencila · 102 tokens

simplify-codebase

Simplification audit or authorized codebase simplification whose stated objective is to remove accidental complexity. Use for evidence-backed deletion or consolidation of dead code, duplicate state, redundant APIs or layers, ownerless abstractions, obsolete compatibility or design records, and over-engineering in any…

tt-a1i/simplify-codebase · 93 tokens

cyclomatic-complexity

Refactor code to reduce cyclomatic complexity so it stays readable, maintainable, and aligned with the long-term vision of the codebase, not just optimized for AI comprehension. Use whenever the user asks to refactor, simplify, clean up, or review code quality; mentions complexity, maintainability, readability…

saurabhkumar8112/cyclomatic-complexity-skill · 103 tokens

refactor

Refactor code to improve structure and maintainability.

vstorm-co/pydantic-deepagents · 12 tokens

laravel-owasp-security

OWASP Top 10 security audit and secure coding guidelines for Laravel + React/Inertia.js applications. Use when auditing for vulnerabilities ("run OWASP audit", "security review", "check my app security") or writing secure Laravel code involving auth, payments, file uploads, or API design. Triggers on security-related…

AsyrafHussin/agent-skills · 87 tokens

technical-debt

Technical debt inventory, prioritization, and audit for PHP/Laravel (MySQL) and Node/TypeScript/React projects. Use when assessing code health, identifying refactoring candidates, planning debt paydown, or auditing a codebase for accumulated debt. Triggers on "audit technical debt", "find tech debt", "debt inventory"…

AsyrafHussin/agent-skills · 109 tokens