patterns

patterns is a skill for Claude Code, Codex from williamzujkowski/standards. It costs 11 tokens per session (435 once invoked), scanned A, original, MIT.

A guide to common software architecture patterns and implementation practices. It covers choosing patterns, handling errors, logging, testing, performance, security, and documenting public interfaces.

In plain words
What is it for?
Use it when planning or reviewing an architecture, selecting an implementation pattern, adding tests and error recovery, or documenting an interface.
Why use it?
It gives developers a checklist for making code easier to maintain and safer to change. It also points out common implementation concerns before they become defects.

Skill for Claude CodeCodex

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

Good fit Use it when planning or reviewing an architecture, selecting an implementation pattern, adding tests and error recovery, or documenting an interface.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/williamzujkowski/standards/patterns
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 williamzujkowski/standards --skill patterns
Clone the repo
git clone --depth 1 https://github.com/williamzujkowski/standards

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 patterns

README.md
[![agentmods](https://agentmods.dev/badge/skills/williamzujkowski/standards/patterns/github.svg)](https://agentmods.dev/skills/williamzujkowski/standards/patterns)
Your own site
<a href="https://agentmods.dev/skills/williamzujkowski/standards/patterns"><img src="https://agentmods.dev/badge/skills/williamzujkowski/standards/patterns/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 patterns

Your own site · 80×15
<a href="https://agentmods.dev/skills/williamzujkowski/standards/patterns"><img src="https://agentmods.dev/badge/skills/williamzujkowski/standards/patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 435 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.00011 $0.00435
Opus 5.5 $0.00004 $0.00174
Sonnet 5.5 $0.00002 $0.00087
Haiku 4.5 $0.00001 $0.00044

Measured yesterday against content hash 36265579318f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-30, from the pricing page.

Security

Grade A, and why

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

skills/architecture/patterns/SKILL.md · 84 lines

What it actually says

Patterns

Quick Navigation: Level 1: Quick Start (5 min) → Level 2: Implementation (30 min) → Level 3: Mastery (Extended)


Level 1: Quick Start

Core Principles

  1. Best Practices: Follow industry-standard patterns for architecture
  2. Security First: Implement secure defaults and validate all inputs
  3. Maintainability: Write clean, documented, testable code
  4. Performance: Optimize for common use cases

Essential Checklist

  • Follow established patterns for architecture
  • Implement proper error handling
  • Add comprehensive logging
  • Write unit and integration tests
  • Document public interfaces

Quick Links to Level 2


Level 2: Implementation

Core Concepts

This skill covers essential practices for architecture.

Key areas include:

  • Architecture patterns
  • Implementation best practices
  • Testing strategies
  • Performance optimization

Implementation Patterns

Apply these patterns when working with architecture:

  1. Pattern Selection: Choose appropriate patterns for your use case
  2. Error Handling: Implement comprehensive error recovery
  3. Monitoring: Add observability hooks for production

Common Pitfalls

Avoid these common mistakes:

  • Skipping validation of inputs
  • Ignoring edge cases
  • Missing test coverage
  • Poor documentation

Level 3: Mastery Resources

Reference Materials

Templates

See the templates/ directory for starter configurations.

External Resources

Consult official documentation and community best practices for architecture.

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. yesterday First seen · 84 lines · 11 tokens per session scan A 36265579318f

Subscribe to this mod's changes

patterns is a skill published in the GitHub repository williamzujkowski/standards (18 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 435 once invoked, about $0.0000 per session on Opus 5.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-29.

Related

Other skills, from other repositories

hr-onboarding

A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".

nexu-io/open-design · 62 tokens

book-mirror

Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…

garrytan/gbrain · 138 tokens

exam-forecast

Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.

anthropics/claude-for-legal · 73 tokens

miniapp

Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.

yc-software/qm · 25 tokens

eli5

Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.

companion-inc/feynman · 63 tokens

deck-course-module

A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.

nexu-io/html-anything · 25 tokens