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.
npx agentmods add skills/tasanakorn/cc-marketplace/python-code-reviewnpx skills add tasanakorn/cc-marketplace --skill python-code-reviewgit clone --depth 1 https://github.com/tasanakorn/cc-marketplaceWrote 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/tasanakorn/cc-marketplace/python-code-review)<a href="https://agentmods.dev/skills/tasanakorn/cc-marketplace/python-code-review"><img src="https://agentmods.dev/badge/skills/tasanakorn/cc-marketplace/python-code-review.svg" alt="Measured on agentmods" 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 | $0.00059 | $0.02995 |
| Opus 5 | $0.00030 | $0.01497 |
| Sonnet 5 | $0.00012 | $0.00599 |
| Haiku 4.5 | $0.00006 | $0.00299 |
Grade A, and why
python-code-review 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 3d 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 — 466 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python Code Review Skill
A specialized skill for reviewing Python code with focus on PEP8 compliance, type hints, modern best practices, and code quality.
Overview
This skill enables Claude to autonomously review Python code for compliance with modern Python standards, including PEP8 style guidelines, type hint coverage, proper structure, and common anti-patterns. It promotes clean, maintainable, and type-safe Python code.
Capabilities
When activated, this skill provides:
-
PEP8 Compliance Review
- Check naming conventions (snake_case, PascalCase)
- Verify line length (88 characters)
- Review whitespace and indentation
- Check import ordering and grouping
- Validate docstring presence and format
-
Type Hints Validation
- Ensure all functions have type hints
- Check for proper return type annotations
- Validate use of modern type syntax (list[], dict[] over List[], Dict[])
- Verify Optional[] vs None union types
- Check for Any types (discourage overuse)
-
Code Structure & Organization
- Review module structure and imports
- Check for proper
__init__.pyusage - Validate entry points (
__main__.py) - Review function/class organization
- Assess module coupling and cohesion
-
Best Practices Enforcement
- Check for use of context managers (with statements)
- Validate exception handling
- Review string formatting (f-strings preferred)
- Check for proper constant definitions
- Assess use of comprehensions vs loops
-
Common Anti-Patterns Detection
- Mutable default arguments
- Bare except clauses
- Using
globalkeyword unnecessarily - Poor variable naming
- Overly complex functions (high cyclomatic complexity)
-
Documentation Quality
- Check for docstrings on public functions/classes
- Validate docstring format (Google/NumPy style)
- Review parameter documentation
- Check for return value documentation
- Assess example usage in docstrings
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.
- 3d ago First seen · 466 lines · 59 tokens per session scan A c91e1f06cd5a
python-code-review is a skill published in the GitHub repository tasanakorn/cc-marketplace (2 stars, last pushed 5mo ago), licensed MIT. It adds 59 tokens to every session and 2,995 once invoked, about $0.0003 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-31.
Other skills, from other repositories
bump-dependency
Bumps a Python package dependency across Home Assistant Core integrations, regenerates core requirement files, runs verification tests and prek lint, and prepares a pull request with proper release/compare links.
implementation-strategy
Choose compatibility-aware scope for runtime and API changes in openai-agents-python. Use before initial implementation and each review-feedback batch to decide whether to patch, reset the design, preserve compatibility, or reject unsupported cases.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
marimo-pair
Work inside the user's live marimo notebook from the code editor: run Python in the same kernel the user does, inspect live notebook state, and commit durable notebook changes through code mode. Use whenever you create, analyze, or improve the user's marimo notebook.
coding
编写并运行 Python 代码,验证脚本逻辑和输出。.
uv
Use uv instead of pip/python/venv. Run scripts with uv run script.py, add deps with uv add, use inline script metadata for standalone scripts.