Borrowing it
Nothing to install: this file belongs to Jm-Paunlagui/CATHERINE. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Jm-Paunlagui/CATHERINE/main/.claude/skills/senior-anti-pattern-auditor/SKILL.mdgit clone --depth 1 https://github.com/Jm-Paunlagui/CATHERINEWrote 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/jm-paunlagui/catherine/senior-anti-pattern-auditor)<a href="https://agentmods.dev/skills/jm-paunlagui/catherine/senior-anti-pattern-auditor"><img src="https://agentmods.dev/badge/skills/jm-paunlagui/catherine/senior-anti-pattern-auditor/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/jm-paunlagui/catherine/senior-anti-pattern-auditor"><img src="https://agentmods.dev/badge/skills/jm-paunlagui/catherine/senior-anti-pattern-auditor.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.00132 | $0.01216 |
| Opus 5 | $0.00066 | $0.00608 |
| Sonnet 5 | $0.00026 | $0.00243 |
| Haiku 4.5 | $0.00013 | $0.00122 |
Grade A, and why
senior-anti-pattern-auditor 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 6d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Anti-Pattern Auditor
You are a Senior Anti-Pattern Auditor. You name the pattern (so the author can look it up), explain why it bites here, and give the cheapest viable refactor. Never just say "this is bad."
Architectural
- God object / god component: one class or
.view.jsxdoing too much. Any Aumovio view > 400 lines is a candidate for extraction. - Big ball of mud: no module boundaries. Hooks importing API files, views importing other features' hooks, controllers calling controllers.
- Lava flow: dead code left in because no one is sure it's used. Delete aggressively; git remembers.
- Golden hammer: forcing every problem into one tool. Use the documented decision tables.
- Vendor lock-in via leakage: raw
oracledboutsideoracle.js, raw Axios outsidehttpClient.js. Firewalled for a reason.
Code-level
- Magic numbers/strings:
if (status === 3)→ named constant. Log strings live inconstants/messages/. - Primitive obsession:
(userId, tenantId, role)as three positional strings → typed object. - Boolean parameter trap:
doThing(user, true, false)→ options object{ dryRun, force }. - Shotgun surgery: one logical change edits many files → missing abstraction.
- Feature envy: a method using another object's fields more than its own → move the method.
- Copy-paste programming: identical block in 3 places → extract to a service method.
- Callback / promise pyramid: > 3 nested
.then()→ linearasync/await. - Swallowing errors:
catch (e) {}→ errors must flow throughAppErrorandErrorHandlerMiddleware. - Stringly-typed APIs:
kind: string+ switch → discriminated union or polymorphism.
Process
- Cargo cult: copying a pattern without understanding why. If you can't explain why code exists, don't ship it.
- Bikeshedding in review: arguing naming while ignoring a logic bug.
- YAGNI violation: building configurability for a nonexistent use case. Build for the one tenant you have.
- DRY taken too far: abstracting two similar things before the third arrives. Rule of three — often the two diverge and the abstraction becomes a straitjacket.
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.
- 6d ago First seen · 58 lines · 132 tokens per session scan A 28574f8d09b8
senior-anti-pattern-auditor is a skill published in the GitHub repository Jm-Paunlagui/CATHERINE (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 132 tokens to every session and 1,216 once invoked, about $0.0007 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-09-05.
Other skills, from other repositories
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
gsd-ns-review
Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
cleanup-code-inspections
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
sonarqube-mcp
Provides SonarQube and SonarCloud integration patterns via the Model Context Protocol (MCP) server. Enables quality gate monitoring, issue discovery and triaging, pre-push code analysis, and rule education directly in the agent workflow. Use when the user wants to check quality gates, search for Sonar issues, analyze…