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 ArabelaTso/Skills-4-SE --skill incremental-python-programmergit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/incremental-python-programmer)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/incremental-python-programmer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/incremental-python-programmer.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.1 | $0.00110 | $0.03123 |
| Opus 5 | $0.00055 | $0.01562 |
| Sonnet 5 | $0.00022 | $0.00625 |
| Haiku 4.5 | $0.00011 | $0.00312 |
Grade A, and why
incremental-python-programmer 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 — 547 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incremental Python Programmer
Implement new features in Python repositories with automated testing and validation.
Workflow
1. Understand the Feature Request
Parse the request:
- Identify what functionality is being requested
- Determine scope (function, class, module, or modification)
- Understand expected behavior and inputs/outputs
- Note any specific requirements or constraints
Clarify if needed:
- Ask about edge cases
- Confirm integration points
- Verify expected behavior
- Check for dependencies
2. Analyze Repository Structure
Automated analysis:
python scripts/analyze_repo_structure.py <repo_path>
Manual analysis:
- Identify relevant modules and files
- Understand existing code organization
- Find similar existing implementations
- Locate test directory structure
- Check coding conventions and patterns
Key questions:
- Where should the new code be placed?
- What existing code needs modification?
- What dependencies are needed?
- What patterns should be followed?
See implementation-patterns.md for common patterns.
3. Plan Implementation
Determine implementation approach:
For new functions:
- Identify appropriate module
- Determine function signature
- Plan implementation logic
- Identify dependencies
For new classes:
- Identify appropriate module or create new one
- Design class structure and methods
- Plan initialization and attributes
- Consider inheritance if applicable
For new modules:
- Determine module name and location
- Plan module structure
- Identify exports and public API
- Plan integration with existing code
For modifications:
- Identify code to modify
- Plan backward compatibility
- Determine parameter additions
- Plan integration with existing logic
4. Implement the Feature
Follow this order:
Step 1: Add necessary imports
# Standard library
import os
from typing import List, Dict, Optional
# Third-party (add to requirements.txt if new)
import requests
# Local imports
from .existing_module import helper_function
What ships with it
3 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.
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 · 547 lines · 110 tokens per session scan A 0f0dd6fd7c3f
incremental-python-programmer is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (248 stars, last pushed 17d ago), licensed Apache-2.0. It adds 110 tokens to every session and 3,123 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
pytest
Provides comprehensive guidance for pytest testing framework including test writing, fixtures, parametrization, mocking, and plugins. Use when the user asks about pytest, needs to write Python tests, use pytest fixtures, or configure pytest for Python projects.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
adk-verify-snippets
Checks that every Python code block in a Markdown file actually compiles and runs, by extracting each block to a temporary file, executing it in an isolated subprocess, and writing a pass/fail report with per-snippet coverage. Use when the user asks to verify, test, or validate the code samples in a README, a guide…
adk-setup
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test run. Runs only when explicitly requested, never on its own. Use when asked to set up, bootstrap, or repair a development…
test-generator
Generate pytest test cases for Python functions and classes.
111-java-maven-dependencies
Use when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a…