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 woliveiras/geremmyas --skill python-ci-setupgit clone --depth 1 https://github.com/woliveiras/geremmyasWrote 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/woliveiras/geremmyas/python-ci-setup)<a href="https://agentmods.dev/skills/woliveiras/geremmyas/python-ci-setup"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/python-ci-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/woliveiras/geremmyas/python-ci-setup"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/python-ci-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.00056 | $0.01410 |
| Opus 5.5 | $0.00022 | $0.00564 |
| Sonnet 5.5 | $0.00011 | $0.00282 |
| Haiku 4.5 | $0.00006 | $0.00141 |
Grade A, and why
python-ci-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 2mo 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python CI Setup
Multi-step workflow to create a production-grade Python CI pipeline.
When to Use
- New Python project needs CI from scratch
- Existing project has incomplete or fragile CI
- Adding security scanning, multi-version testing, or Trusted Publishing
Pipeline Layers (in order)
Each layer gates the next. If a layer fails, the pipeline stops.
- Format —
ruff format --check .(orblack --check .) must pass - Lint —
ruff check .(orflake8) must pass - Type check —
mypy src(or Pyright) must pass - Test —
pytestwith coverage threshold - Security scan —
bandit -r src+pip-audit - Build —
python -m buildproduces valid sdist/wheel - Publish (optional) — Trusted Publishing to PyPI via OIDC
Steps
1. Choose CI Platform
Default to GitHub Actions for GitHub-hosted repositories. Ensure matrix testing across supported Python versions (3.11, 3.12, 3.13, 3.14).
2. Create Quality Workflow
For GitHub Actions: .github/workflows/ci.yml
name: CI
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
quality:
runs-on: ubuntu-latest
strategy:
matrix:
python-version: ["3.11", "3.12", "3.13", "3.14"]
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: ${{ matrix.python-version }}
- run: python -m pip install -U pip
- run: python -m pip install -e ".[dev]"
- run: ruff format --check .
- run: ruff check .
- run: mypy src
- run: pytest --tb=short
- run: coverage run -m pytest && coverage report --fail-under=85
- run: bandit -r src
- run: pip-audit
3. Configure Tools in pyproject.toml
All tool configuration lives in pyproject.toml:
[tool.ruff]
line-length = 100
target-version = "py311"
[tool.ruff.lint]
select = ["E", "F", "I", "B", "UP"]
[tool.pytest.ini_options]
testpaths = ["tests"]
addopts = "-ra"
[tool.coverage.run]
branch = true
source = ["src/my_package"]
[tool.coverage.report]
fail_under = 85
[tool.mypy]
python_version = "3.11"
strict = true
mypy_path = ["src"]
[tool.bandit]
exclude_dirs = ["tests"]
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.
- 2mo ago First seen · 203 lines · 56 tokens per session scan A e86f78b02901
python-ci-setup is a skill published in the GitHub repository woliveiras/geremmyas (10 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 1,410 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.
python-ci-setup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| python-ci-setupwoliveiras/geremmyas | Skill | 10 | 3mo ago | MIT | A | 56 | Claude Code, Codex |
| pypi-ops0xDarkMatter/claude-mods | Skill | 79 | 7d ago | MIT | A | 74 | Claude Code |
| uv-package-managerGalaxy-Dawn/claude-scholar | Skill | 6.0k | 18d ago | MIT | C | 42 | Claude Code |
| ci-cdoborchers/fractional-cto | Skill | 36 | 12d ago | MIT | A | 80 | Claude Code |
| simple-modern-uvjlevy/simple-modern-uv | Skill | 303 | 2mo ago | MIT | A | 98 | Claude Code, Codex |
| python-deploynixopus/nixopus | Skill | 1.5k | 5d ago | none | A | 53 | Claude Code, Codex |
| scaffold-pythonurmzd/dotfiles | Skill | 6 | 3d ago | Apache-2.0 | A | 135 | Claude Code |