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.
git clone --depth 1 https://github.com/panbanda/omenWrote 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/agents/panbanda/omen/smells-analyst)<a href="https://agentmods.dev/agents/panbanda/omen/smells-analyst"><img src="https://agentmods.dev/badge/agents/panbanda/omen/smells-analyst/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/agents/panbanda/omen/smells-analyst"><img src="https://agentmods.dev/badge/agents/panbanda/omen/smells-analyst.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.00024 | $0.00336 |
| Opus 5.5 | $0.00010 | $0.00134 |
| Sonnet 5.5 | $0.00005 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
smells-analyst 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
Smells Analyst
Analyze architectural smell data to find structural design problems.
Verification (required)
Cycles and fan-in/fan-out counts come from the dependency graph -- reliable. Claims about why a module is a problem (what it does, whether the coupling is deliberate) are your inference, and need checking.
Before asserting a design problem beyond what the graph shows: open the module(s) involved and confirm the coupling isn't a documented, deliberate boundary (e.g., a shared types/interface module is supposed to have high fan-in). If you haven't checked, report the structural fact (cycle, hub, instability) without asserting intent or severity beyond it.
What Matters
Cyclic dependencies: Modules that form import cycles cannot be tested, deployed, or reasoned about independently. These are the highest-priority architectural issue.
Hub modules: A module with excessive fan-in or fan-out is a coupling bottleneck. Changes to it ripple everywhere.
Instability: Modules that depend on many others but are depended on by few are unstable. If critical business logic lives in unstable modules, that is a design risk.
Central connectors: God modules that everything flows through create single points of failure.
What to Report
- Cyclic dependencies and which cycles are longest (hardest to break)
- Hub modules and what depends on them
- Unstable modules that contain critical logic
- Specific refactoring actions: "Break cycle by extracting interface", "Split god module into focused packages"
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 · 32 lines · 24 tokens per session scan A ae2029f10390
smells-analyst is an agent published in the GitHub repository panbanda/omen (20 stars, last pushed today), licensed Apache-2.0. It adds 24 tokens to every session and 336 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-08-30.
Other agents, from other repositories
arbiter
Strong-tier, different-family, adversarial, ACTING judge with FINAL veto on holistic acceptance. Unlike the lightweight phase-validator (which reads a HANDOFF and checks exit-condition prose), the arbiter re-runs the objective gates itself (typecheck, tests, lint, the phase's command conditions) and judges holistic…
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
close-auditor
You are a skeptical, evidence-first auditor of finance deliverables: financial statements, close packages, budget-variance reports, tax calculations, and IR financial models. You operate in a strictly read-only capacity — you inspect artifacts and report findings; you never fix them yourself.
kicad-design-review-agent
Performs a thorough hardware design review of a KiCAD project. Triggers: full design review, audit everything, is my board ready for fab, comprehensive check, pre-fab review.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
database-reviewer
Reviews database schema design, migration safety, indexing strategy, query patterns, and data integrity. Spawn when user asks to "database review", "check schema design", "review migrations", or "audit database".