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 sethdford/claude-skills --skill architecture-anti-patternsgit clone --depth 1 https://github.com/sethdford/claude-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/sethdford/claude-skills/architecture-anti-patterns)<a href="https://agentmods.dev/skills/sethdford/claude-skills/architecture-anti-patterns"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/architecture-anti-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/sethdford/claude-skills/architecture-anti-patterns"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/architecture-anti-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.00028 | $0.00757 |
| Opus 5 | $0.00014 | $0.00378 |
| Sonnet 5 | $0.00006 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
architecture-anti-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 11d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Anti-Patterns
Recognize and avoid common architectural mistakes that lead to fragility, complexity, or failure.
Context
You are reviewing an architecture and want to spot common anti-patterns. Patterns of failure repeat across organizations. Learn them, recognize them, guide teams away from them.
Domain Context
Based on architecture and design anti-patterns research:
- God Object: One class/service responsible for too much. Hard to change, test, understand.
- Big Ball of Mud: No clear architecture. Code accretion with no structure. Hard to modify without breaking things.
- Circular Dependency: A depends on B, B depends on A. Can't use A without B, vice versa. Breaks modularity.
- Database as Integration Point: Services share database schema. Schema changes break all services. No independence.
- Premature Optimization: Design for 10x scale when you have 1x. Overcomplex, unmaintainable.
Instructions
-
Common Anti-Patterns and Recognition:
- Monolith Bloat: Hundreds of thousands of lines in one service. Deploys take 30 min. Hard to test. Fix: decompose into services by business domain.
- Tight Coupling: Service A calls Service B calls Service C synchronously. Cascade failure: A down → B unavailable → C affected. Fix: async, timeouts, circuit breakers, fallbacks.
- No Logging/Monitoring: Don't know what's happening in production. Outage takes hours to debug. Fix: structured logging, metrics, distributed tracing, alerts.
- Cache Invalidation Chaos: Cache stale data, inconsistency everywhere. Fix: cache strategy with TTL, event-driven invalidation, don't cache mutable shared state.
- N+1 Query Problem: Loop calls database for each item. 1000 items = 1000 queries. Fix: batch queries, join tables, fetch aggregates.
-
Diagnose When Present:
- Performance issues in service you don't touch? Likely tight coupling or cascade failure.
- Hard to understand request path? Likely circular dependencies or god objects.
- Frequent outages from unrelated changes? Likely shared database or tight coupling.
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.
- 11d ago First seen · 53 lines · 28 tokens per session scan A 7b8d6785cf98
architecture-anti-patterns is a skill published in the GitHub repository sethdford/claude-skills (40 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 757 once invoked, about $0.0001 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-30.
Other skills, from other repositories
cmd_flutter_review
Review Flutter/Dart code for idiomatic patterns, widget best practices, state management, performance, accessibility, and security. Invokes the flutter-reviewer agent.
cmd_code_review
Code review — local uncommitted changes or GitHub PR (pass PR number/URL for PR mode).
cmd_cpp_review
Comprehensive C++ code review for memory safety, modern C++ idioms, concurrency, and security. Invokes the cpp-reviewer agent.
cmd_go_review
Comprehensive Go code review for idiomatic patterns, concurrency safety, error handling, and security. Invokes the go-reviewer agent.
coding-standards
Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
santa-method
Multi-agent adversarial verification with convergence loop. Two independent review agents must both pass before output ships.