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 skills add mickeyyaya/refactoring-skills --skill design-patterns-behavioralgit clone --depth 1 https://github.com/mickeyyaya/refactoring-skillsWrote 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.
[](https://agentmods.dev/skills/mickeyyaya/refactoring-skills/design-patterns-behavioral)<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/design-patterns-behavioral"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/design-patterns-behavioral/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.
<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/design-patterns-behavioral"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/design-patterns-behavioral.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00040 | $0.03136 |
| Opus 5 | $0.00020 | $0.01568 |
| Sonnet 5 | $0.00008 | $0.00627 |
| Haiku 4.5 | $0.00004 | $0.00314 |
Grade A, and why
design-patterns-behavioral 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 10d 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Patterns: Behavioral
Overview
Behavioral patterns address how objects communicate and distribute responsibility. They replace tangled conditional logic, tight coupling, and ad-hoc event wiring with well-named structures. Recognizing which pattern is — or should be — present is a core code review skill.
When to Use
- Large
switch/if-elseblocks branching on type or state - Tightly coupled objects calling each other in every direction
- Duplicated algorithm logic with only small steps varying
- Event/notification systems needing correctness and scalability review
Quick Reference
| Pattern | Core Problem Solved | Key Red Flag |
|---|---|---|
| Chain of Responsibility | Decouple sender from receiver; multiple handlers | Hardcoded handler cascade in caller |
| Command | Encapsulate request as object; undo/queue | Method calls not storable or reversible |
| Iterator | Uniform traversal without exposing internals | Callers access internal array fields directly |
| Mediator | Replace many-to-many with central coordinator | Objects holding refs to many unrelated peers |
| Memento | Save/restore state without breaking encapsulation | Caller copies internal fields for undo |
| Observer | Notify dependents of state changes automatically | Producer manually calls every consumer |
| State | Object changes behavior as state changes | Giant switch (this.state) in multiple methods |
| Strategy | Interchangeable algorithms at runtime | if (type === 'A') algoA() else algoB() |
| Template Method | Fix algorithm structure; vary steps | Copy-pasted algorithm with 1-2 lines differing |
| Visitor | Add operations without modifying hierarchy | New instanceof branch per operation |
| Interpreter | Evaluate sentences in a simple grammar | Ad-hoc string parsing scattered across codebase |
Behavioral Patterns
1. Strategy (most commonly applied)
Intent: Define a family of algorithms, encapsulate each one, and make them interchangeable.
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.
- 10d ago First seen · 320 lines · 40 tokens per session scan A 702f064c923a
design-patterns-behavioral is a skill published in the GitHub repository mickeyyaya/refactoring-skills (6 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 3,136 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…