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 skills add ondrasek/cc-plugins --skill python-setupgit clone --depth 1 https://github.com/ondrasek/cc-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/skills/ondrasek/cc-plugins/python-setup)<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/python-setup"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/python-setup/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/ondrasek/cc-plugins/python-setup"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/python-setup.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.00062 | $0.00735 |
| Opus 5.5 | $0.00025 | $0.00294 |
| Sonnet 5.5 | $0.00012 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
python-setup 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python Setup
Critical Rules
- Always present analysis and plan to the user before making changes
- Merge, don't replace — preserve existing pyproject.toml sections, CI jobs, hooks
- Use the package manager detected in analysis (don't assume uv)
- All hook scripts must be executable (
chmod +x)
Context Files
Read these files before starting:
skills/shared/references/methodology-framework.md— shared principles, hook architecture, exit codes, settings.json formatskills/shared/references/setup-workflow.md— the 6-phase workflow structureskills/python-setup/references/methodology.md— Python-specific 9 dimensions, thresholds, tool research guidanceskills/python-setup/references/analysis-checklist.md— what to check in the target codebaseskills/python-setup/templates/— annotated examples showing structural patterns. Use templates for patterns but substitute the tools chosen during research.
Workflow
Follow the 6-phase workflow from setup-workflow.md.
Phase 1: Analyze
Follow analysis-checklist.md systematically: package manager, Python version, project structure, frameworks, existing tools, CI, maturity.
Phase 2: Plan
Research tools for each of the 9 dimensions. Python-specific files to plan:
pyproject.toml—[tool.*]sections for each tool.claude/hooks/— quality-gate.sh, per-edit-fix.sh, session-start.sh, optionally auto-commit.sh.claude/settings.json— hook registrations (see methodology-framework.md for format).github/workflows/ci.yml— CI pipeline.pre-commit-config.yaml— pre-commit hooksMakefile— development commandsCLAUDE.md— project instructionspyrightconfig.json— type checker config (only if pyright chosen)semver-check.sh— only when Dimension 9 is activated at level 3
Present complete plan and wait for approval. Ask about optional items (auto-commit, style-guide check).
Phase 3: Configure
Read each template in templates/ for the structural pattern, substitute the researched tools. Install dev dependencies and pre-commit hooks.
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/analysis-checklist.md 6.2 KB
- references/methodology.md 21 KB
- references/reviewer-prompt.md 3.7 KB
- templates/auto-commit.sh 3.2 KB runs code
- templates/ci.yml 3.3 KB
- templates/CLAUDE.md 459 B
- templates/gitignore 4.6 KB
- templates/Makefile 1.3 KB
- templates/per-edit-fix.sh 2.9 KB runs code
- templates/pre-commit-config.yaml 406 B
- templates/pyproject-tools.toml 3.0 KB
- templates/pyrightconfig.json 576 B
- templates/quality-gate.sh 8.5 KB runs code
- templates/semver-check.sh 4.1 KB runs code
- templates/session-start.sh 1.3 KB runs code
- templates/style-guide-check.sh 2.0 KB runs code
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 · 72 lines · 62 tokens per session scan A 8b25980bed95
python-setup is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 62 tokens to every session and 735 once invoked, about $0.0002 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-31.
Other skills, from other repositories
uv-package-manager
Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows. Use when setting up Python projects, managing dependencies, or optimizing Python development workflows with uv.
pypi-ops
Publish Python packages to PyPI via OIDC Trusted Publishing (PEP 740 attestations, gh-action-pypi-publish) instead of stored tokens. Use for: invalid-publisher errors, pending-publisher 404s, uv publish/twine, TestPyPI, environment approval gates, and rotating/auditing publish tokens.
ci-cd
This skill should be used when the user is setting up GitHub Actions, configuring CI/CD pipelines, creating test matrices, enabling trusted publishing with OIDC, automating PyPI releases, adding Dependabot or Renovate, or configuring Sigstore attestations. Covers workflow architecture…
simple-modern-uv
Start, selectively modernize, fully migrate, or update Python projects using simple-modern-uv practices: uv, ruff, BasedPyright, pytest, GitHub Actions CI, and tag-driven PyPI publishing. Use when creating a Python project; adding selected tooling or repository practices to an existing project; migrating from Poetry…
python-deploy
Build and deploy Python applications — uv, poetry, pdm, pipenv, pip, framework detection, and Dockerfile patterns. Use when deploying a Python project, or when requirements.txt, pyproject.toml, or Pipfile is detected.
setup-python-project
Scaffold a new Python project with uv, ruff, pytest, and GitHub Actions CI. Use when the user says "set up a new Python project", "scaffold a project", "create a new Python app", or similar.