laravel-truss: Command for Claude Code

.claude/commands/code-smell.md

code-smell is a command for Claude Code from albertoarena/laravel-truss. It costs 18 tokens per session (1,781 once invoked), scanned A, original, MIT.

A source-code audit that looks for code smells and architectural problems, then records verified findings in an AUDIT.md file. Code smells are patterns that may make software harder to change or understand.

In plain words
What is it for?
Use it to review first-party source, exclude generated or vendored files, and document actionable design and maintainability issues.
Why use it?
It gives maintainers a checked list of problems without changing the application code or tests.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md; mentions subagents; mentions AGENTS.md.

This is albertoarena/laravel-truss's own configuration. It tells Claude Code how to work on laravel-truss itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything laravel-truss configures →

Reuse

Borrowing it

Nothing to install: this file belongs to albertoarena/laravel-truss. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/albertoarena/laravel-truss/main/.claude/commands/code-smell.md
Clone the repo
git clone --depth 1 https://github.com/albertoarena/laravel-truss

Made for: Claude Code.

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 code-smell

README.md
[![agentmods](https://agentmods.dev/badge/commands/albertoarena/laravel-truss/code-smell/github.svg)](https://agentmods.dev/commands/albertoarena/laravel-truss/code-smell)
Your own site
<a href="https://agentmods.dev/commands/albertoarena/laravel-truss/code-smell"><img src="https://agentmods.dev/badge/commands/albertoarena/laravel-truss/code-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 code-smell

Your own site · 80×15
<a href="https://agentmods.dev/commands/albertoarena/laravel-truss/code-smell"><img src="https://agentmods.dev/badge/commands/albertoarena/laravel-truss/code-smell.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,781 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.
Origin original No closer match found 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.00018 $0.01781
Opus 5.5 $0.00007 $0.00712
Sonnet 5.5 $0.00004 $0.00356
Haiku 4.5 $0.00002 $0.00178

Measured 29d ago against content hash 5acfb2b61746, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-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 29d 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.

.claude/commands/code-smell.md · 97 lines

How it starts

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

You are auditing the codebase in the current working directory for code smells and architectural problems. The goal is an audit the maintainers can act on. Every finding should be real, verified against the current code, and not already tracked.

Inputs. Use these defaults unless the user overrides them:

  • Tracker file: AUDIT.md at the repo root. Create it if it's missing; add to new file if it exists.
  • Scope: all first-party source. Exclude vendored, generated and build output (vendor/, node_modules/, dist/, build/, lockfiles, migrations' generated SQL, compiled assets).
  • Changes allowed: the tracker file only. Don't edit source or tests, and don't commit.

Before you start

Learn the project before judging it.

  1. Read the guidance files that exist: CLAUDE.md, AGENTS.md, CONTRIBUTING.md, the README's architecture or contributing sections, and ADRs or docs/architecture*.
  2. Read the linter, formatter and type-checker configs (for example phpstan.neon, pint.json, .eslintrc*, tsconfig.json, pyproject.toml, rector.php, biome.json). Their rules, and especially their ignores, show deliberate choices.
  3. Read the dependency manifest (composer.json, package.json, go.mod, Cargo.toml, pyproject.toml) so you know the framework, and don't flag its idioms as smells.
  4. Run git log --oneline -20 and git status so you know what just changed and what is uncommitted. Trust only what you read in this session.
  5. If the tracker file exists, read it in full. Anything already in it, including items marked won't-do or rejected and their reasons, is out of scope. Don't re-report it in different words.

From these, write down for yourself the project's deliberate conventions. Examples: "no final classes", "immutable value objects", "functions over classes", "errors as return values", "barrel files per module". Treat each one as a design decision, not a smell, but do report code that breaks it. When a convention is only implied by consistent practice across the codebase, follow it too.

Then map the structure: top-level modules or packages, entry points (HTTP routes, CLI commands, jobs, exported public API), and the rough size of each area.

Read the full file on GitHub · 97 lines

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. 29d ago First seen · 97 lines · 18 tokens per session scan A 5acfb2b61746

Subscribe to this mod's changes

code-smell is a command published in the GitHub repository albertoarena/laravel-truss (291 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 1,781 once invoked, about $0.0001 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-26.