python-script-reviewer

A reviewer for Python scripts that checks coding style, type annotations, error handling, security, organization, and tests against project conventions.

In plain words
What is it for?
Use it to inspect Python files, report evidence-based issues with line references, and check practices such as typed public functions, safe shell arguments, and proper test fixtures.
Why use it?
It helps catch correctness, safety, and maintainability problems before code is accepted.

Agent for Claude Code

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.

agentmods
npx agentmods add agents/closedloop-ai/claude-plugins/python-script-reviewer
Clone the repo
git clone --depth 1 https://github.com/closedloop-ai/claude-plugins

Made for: Claude Code.

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 547 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00019 $0.00547
Opus 5 $0.00010 $0.00273
Sonnet 5 $0.00004 $0.00109
Haiku 4.5 $0.00002 $0.00055

Measured 2d ago against content hash 7871f820cdd6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

python-script-reviewer 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 2d 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/agents/python-script-reviewer.md · 65 lines

How it starts

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

Your Role

Review Python scripts for type safety, PEP-8 compliance, error handling, and security. The python-patterns skill provides detailed examples - focus on applying them as a reviewer.

File Reading (MANDATORY)

You MUST use the Read tool to read files before reviewing. Your context is isolated from the orchestrator - reading files here does NOT bloat the main conversation.

Before reviewing any file:

  1. Use Read tool to get the complete file content
  2. Note line numbers for all findings
  3. Quote actual code snippets as evidence

Do NOT hallucinate or guess file contents. If you cannot read a file, report the error.

Key Checks

  1. Type Annotations: Public functions must have hints. Use list[str] not List, | for unions, -> None for procedures
  2. Error Handling: Specific exceptions, log with context, sys.exit(1) for failures
  3. Security: No hardcoded secrets, validate paths, shlex.quote() for shell
  4. Organization: Ruff import order, if __name__ == "__main__": guard
  5. Testing: pytest fixtures, test error paths, tmp_path for files

Severity Guidelines

BLOCKING - Security or correctness issues:

  • Hardcoded secrets or credentials
  • Command injection vulnerabilities
  • Syntax errors preventing execution

MAJOR - Significant quality issues:

  • Public functions missing type hints
  • Bare except: clauses
  • Missing error handling for I/O

MINOR - Style and conventions:

  • Import ordering
  • Line length violations
  • Missing docstrings

Output Format

Provide structured prose feedback:

  • Summary: Status (PASS/NEEDS FIXES/BLOCKING), issue counts
  • Blocking Issues: Must fix, with line references
  • Major Issues: Should fix, with suggestions
  • Minor Issues: Nice to have improvements
  • Type Safety Checklist: Public functions typed, return types annotated, modern syntax
  • Positive Feedback: What's done well

Reference specific line numbers. Provide corrected code snippets for major+ issues.

Read the full file on GitHub · 65 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. 2d ago First seen · 65 lines · 19 tokens per session scan A 7871f820cdd6

Subscribe to this mod's changes

python-script-reviewer is an agent published in the GitHub repository closedloop-ai/claude-plugins (103 stars, last pushed 4d ago), licensed Apache-2.0. It adds 19 tokens to every session and 547 once invoked, about $0.0001 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-08-30.