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 architectural-patternsgit 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/architectural-patterns)<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/architectural-patterns"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/architectural-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.
<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/architectural-patterns"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/architectural-patterns.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.00038 | $0.02590 |
| Opus 5 | $0.00019 | $0.01295 |
| Sonnet 5 | $0.00008 | $0.00518 |
| Haiku 4.5 | $0.00004 | $0.00259 |
Grade A, and why
architectural-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 9d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architectural Patterns Review Skill
Overview
Architectural patterns define large-scale structure: how major components communicate, dependency direction, and where responsibilities live. Unlike GoF patterns (class level), these operate at module, service, and system level. Review asks: "Are boundaries intact? Are dependencies flowing correctly? Is this component doing work that belongs elsewhere?"
When to Use
- PR adds a new layer dependency or import
- Evaluating whether a new service/module belongs where the author placed it
- Diagnosing why a codebase is hard to test despite "clean" individual classes
- Assessing whether stated architecture matches actual code
Quick Reference
| Pattern | Core Invariant | Key Violation Signal |
|---|---|---|
| MVC | Model never imports View | View contains business logic; fat Controller |
| MVP | View is passive; Presenter mediates | View makes decisions; Presenter imports View type |
| MVVM | ViewModel does not know View | ViewModel imports UI framework types |
| Layered | Dependencies flow downward only | Data layer imports Presentation types |
| Clean Architecture | Inner circles never depend on outer | Entity imports from framework layer |
| Hexagonal | Domain has zero external dependencies | Domain imports HTTP, ORM, or DB libraries |
| Event-Driven | Producers don't know consumers | Producer awaits consumer response synchronously |
| Microservices | Each service owns its data | Shared database across services |
| Repository | Business logic doesn't know storage | Service builds raw SQL or ORM queries directly |
| CQRS | Commands don't return data; Queries don't mutate | Query with side effects; Command returning rows |
Architectural Patterns
1. MVC (Model-View-Controller)
Dependency Direction:
Controller → Model
Controller → View
View → Model (read-only, for rendering)
Model ✗ never imports View or Controller
Key Invariants: Model contains all domain logic with zero UI awareness. Controller orchestrates: reads input, tells Model to change, selects View. View only renders, delegating decisions to Controller.
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.
- 9d ago First seen · 255 lines · 38 tokens per session scan A 1591935425af
architectural-patterns is a skill published in the GitHub repository mickeyyaya/refactoring-skills (6 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 2,590 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…