smell

smell is a skill for Claude Code from smallnest/goal-workflow. It costs 97 tokens per session (9,205 once invoked), scanned A, a copy of smell, MIT.

A codebase review that looks for architecture problems, recurring code-quality issues, inefficient algorithms, and common design anti-patterns. It produces a Markdown report with confirmed findings and possible issues.

In plain words
What is it for?
Use it to inspect a whole project, one module, or recent changes. It helps identify code smells, architectural violations, design-pattern problems, and algorithmic complexity hotspots.
Why use it?
It helps reveal maintenance and performance risks that may be spread across many files. Checking context, callers, history, and measurements helps separate real problems from harmless patterns.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions subagents.

Part of the goal-workflow-skills plugin — 20 skills shipped together

Good fit Use it to inspect a whole project, one module, or recent changes. It helps identify code smells, architectural violations, design-pattern problems, and algorithmic complexity hotspots.

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

Made for: Claude Code.

Or install goal-workflow-skills, the plugin that ships this one along with the rest of its 20 skills.

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 smell

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/smallnest/goal-workflow/smell"><img src="https://agentmods.dev/badge/skills/smallnest/goal-workflow/smell.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 9,205 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. Third-party audits
  • Socket pass 16 Aug 2026
  • Snyk pass 16 Aug 2026
How audits are shown
Origin 89% copy Near-identical to another mod 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.00097 $0.09205
Opus 5.5 $0.00039 $0.03682
Sonnet 5.5 $0.00019 $0.01841
Haiku 4.5 $0.00010 $0.00920

Measured 2mo ago against content hash 0823878cb8b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

smell 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 2mo 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.

Origin

This is a copy

89% identical to smell — 99 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/smell/SKILL.md · 751 lines

How it starts

The opening of the file, as written. The whole thing — 751 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Smell — Architecture Bad Smell Detector

Analyze a codebase to find violations of software architecture principles, anti-patterns, code "bad smells," and algorithmic complexity hotspots. Produce a comprehensive, actionable markdown report.

Knowledge base: This skill encodes architectural patterns, anti-patterns, code smells, and algorithmic complexity heuristics drawn from industry research and practice, including the classic code smells catalog by Martin Fowler / Kent Beck (as organized on refactoring.guru: Bloaters, Object-Orientation Abusers, Change Preventers, Dispensables, Couplers).


The Job

  1. Understand the scope — ask what part of the project to analyze (full project, specific module, or recent changes)
  2. Scan the codebase using find, grep, and Agent (Explore subagent) to gather candidate signals and evidence
  3. Validate candidates against context, callers, history, workload, and measurements before confirming findings
  4. Generate a detailed markdown report saved to tasks/smell-report-[timestamp].md
  5. Present a summary of confirmed findings and separate candidates to the user

Step 1: Scope Clarification

Ask the user:

What scope should I analyze?
  A. Entire project (thorough, may take time)
  B. Specific module/directory: [please specify]
  C. Only recently changed files (git diff)
  D. Only architectural-level issues (skip low-level code smells)

If the user doesn't specify, default to option A for small projects (< 100 files) or C for large projects.


Step 2: Evidence Gathering

Use the Explore subagent (Agent with subagent_type: "Explore") to scan the codebase for architectural patterns and anti-patterns. Run multiple parallel explorations:

Exploration Commands

Run these in parallel to gather evidence efficiently:

  1. Project Structure Scan: Map the directory tree, identify the architectural style (layered, modular monolith, microservices, etc.)
  2. Dependency Analysis: Find import/include patterns, check for circular dependencies, identify coupling hotspots
  3. Module/Component Scan: Identify God Objects (files > 500 lines), check cohesion, check single responsibility violations
  4. Pattern Detection: Look for known anti-pattern signatures (static cling, service locator abuse, leaky abstractions)
  5. Testing Scan: Check test coverage patterns, test file locations, test-to-code ratios
  6. Naming & Clarity Scan: Flag misleading names, overly generic names (Manager, Helper, Util), inconsistent naming conventions
  7. Complexity Scan: Detect algorithmic complexity hotspots — nested loops, N+1 queries, repeated scans, sort-in-loop, expensive recomputation in render paths

Read the full file on GitHub · 751 lines

Files

What ships with it

2 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. 2mo ago First seen · 751 lines · 97 tokens per session scan A 0823878cb8b8

Subscribe to this mod's changes

smell is a skill published in the GitHub repository smallnest/goal-workflow (299 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 9,205 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to smell, differing in 99 lines, and is treated as a copy.

Related

smell compared with skills from other repositories

smell next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
smellsmallnest/goal-workflowSkill2991mo agoMITA97Claude Code
review-resolutionsentimony/skillsSkill72d agoMITA52Claude Code
cross-reviewsentimony/skillsSkill72d agoMITA123Claude Code
verification-gatesentimony/skillsSkill72d agoMITA48Claude Code
review-requestsentimony/skillsSkill72d agoMITA41Claude Code
criticism-self-criticismHughYau/qiushi-skillSkill3.9k1mo agoMITA197Claude Code
validate-issuerichkuo/rk-skillsSkill50yesterdayMITA48Claude Code