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/galaxyproject/claude-galaxy-pluginsWrote 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/commands/galaxyproject/claude-galaxy-plugins/gx-review-business-logic-organization)<a href="https://agentmods.dev/commands/galaxyproject/claude-galaxy-plugins/gx-review-business-logic-organization"><img src="https://agentmods.dev/badge/commands/galaxyproject/claude-galaxy-plugins/gx-review-business-logic-organization/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/commands/galaxyproject/claude-galaxy-plugins/gx-review-business-logic-organization"><img src="https://agentmods.dev/badge/commands/galaxyproject/claude-galaxy-plugins/gx-review-business-logic-organization.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.00000 | $0.01475 |
| Opus 5 | $0.00000 | $0.00737 |
| Sonnet 5 | $0.00000 | $0.00295 |
| Haiku 4.5 | $0.00000 | $0.00147 |
Grade A, and why
gx-review-business-logic-organization 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 12d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Galaxy Code for Controller/Service/Manager Best Practices
Perform a Python code review on the provided code. Accept input in any of the following forms:
- A working directory path (analyze git diff in that directory)
- A Git commit reference (analyze changes in that commit)
- A list of Python file paths (analyze those files)
- A planning document (analyze the Python files in the plan)
Review Criteria
Review the code and ensure it follows Galaxy best practices for what code belongs in controllers, services, and managers:
- Controllers should be thin - Minimal logic, just request/response handling
- Services handle API processing details - Shield application logic from FastAPI internals
- Managers contain business logic - All non-trivial operations should live here
- Models mediate database interactions - Isolate backend from database internals
Galaxy Three-Layer Architecture
┌─────────────────────────────────────────┐
│ API Controllers │ ← Request/Response handling
│ (lib/galaxy/webapps/galaxy/api/) │
├─────────────────────────────────────────┤
│ Services │ ← API processing details (thin layer)
│ (lib/galaxy/webapps/galaxy/ │
│ services/) │
├─────────────────────────────────────────┤
│ Managers │ ← Business logic
│ (lib/galaxy/managers/) │
├─────────────────────────────────────────┤
│ Models │ ← Database interactions (SQLAlchemy ORM)
│ (lib/galaxy/model/) │
├─────────────────────────────────────────┤
│ Database │
└─────────────────────────────────────────┘
Layer Responsibilities
Controllers (API Layer)
- Parse request parameters
- Call service/manager methods
- Format responses
- Handle HTTP-specific concerns
Anti-pattern:
# BAD - business logic in controller
@router.post("/api/histories")
def create_history(payload: CreateHistoryPayload):
history = model.History()
history.name = payload.name
history.user = trans.user
session.add(history)
session.commit()
# Lots of validation, side effects...
return history
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.
- 12d ago First seen · 187 lines · 0 tokens per session scan A a1b557afb1f5
gx-review-business-logic-organization is a command published in the GitHub repository galaxyproject/claude-galaxy-plugins (4 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,475 tokens. 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-31.
Other commands, from other repositories
notebook-review
Comprehensive review of Jupyter notebooks and Python scripts.
python-review
Comprehensive Python code review for PEP 8 compliance, type hints, security, and Pythonic idioms. Invokes the python-reviewer agent.
review-uv-script
Review uv Python script for PEP 723 compliance and best practices.
review-python-code
A command for reviewing Python code for style, type annotations, reliability, performance, and project rules. PEP 8 is the commonly used guide for formatting and writing readable Python.
review-react-code
A command that reviews React and TypeScript code, including how components are organised, how Hooks are used, how state is handled, and how the code performs.
py-harden
Scan Python backend code for anti-patterns and fix them. Runs the full anti-pattern catalog (AP-01 through AP-22) against the codebase.