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 charlieviettq/awesome-agent-skill --skill design-smell-reviewgit clone --depth 1 https://github.com/charlieviettq/awesome-agent-skillWrote 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/charlieviettq/awesome-agent-skill/design-smell-review)<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/design-smell-review"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/design-smell-review/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/charlieviettq/awesome-agent-skill/design-smell-review"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/design-smell-review.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.00051 | $0.00446 |
| Opus 5.5 | $0.00020 | $0.00178 |
| Sonnet 5.5 | $0.00010 | $0.00089 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
design-smell-review 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 1mo 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.
What it actually says
Design smell review
Scope
Review structure and boundaries, not line-by-line style. Pair with PR diff review for changes; use this for module-level health.
Smell checklist
| Smell | Signal | Direction |
|---|---|---|
| God module | Many unrelated responsibilities | Split by domain |
| Shotgun surgery | One change touches many files | Consolidate logic |
| Feature envy | Module A mostly uses B's data | Move behavior |
| Leaky abstraction | Impl details escape API | Narrow public surface |
| Config soup | Magic strings everywhere | Named constants / schema |
| Boolean flags | if is_x branches everywhere |
Polymorphism or strategy |
Workflow
- Map entry points and dependencies (imports, public API).
- List responsibilities per module; flag >1 unrelated core job.
- Check testability — can core logic run without I/O?
- Propose smallest structural improvement (not full rewrite).
- Record decision in ADR if trade-off is significant.
Output format
## Summary
[1-2 sentences]
## Smells (priority order)
1. [Smell] — evidence — suggested fix (effort: S/M/L)
## Recommended next step
[One concrete change to try first]
Simplification (Chesterton's Fence)
Before deleting or collapsing code, ask why it exists:
- Comment, test, or git history explaining constraint?
- If unknown, prefer small experiment or question over bulk delete.
- Remove duplication only when behavior is proven identical.
- "Fewer lines" is not success if edge cases or observability regress.
Boundaries
- Do not block small fixes on perfect architecture.
- Prefer incremental extraction over big-bang rewrites.
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.
- 1mo ago First seen · 58 lines · 51 tokens per session scan A 99c6ced52908
design-smell-review is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (26 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 446 once invoked, about $0.0002 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-03.
Other skills, from other repositories
refactor-advisor
A code review helper that finds common design and maintenance problems in a codebase and suggests ways to restructure the code.
zh-code-reviewer
A Chinese-language code-review specialist that produces a structured review report. It examines coding style, possible bugs, performance, security, and design choices.
luna
Reviews code for objective correctness, security, and reliability.
max
Cleans up and improves existing code without changing behavior.
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
andrej-karpathy
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.