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 commands/flz/iaqualink-py/update-python-versiongit clone --depth 1 https://github.com/flz/iaqualink-pyWhat 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.00011 | $0.00847 |
| Opus 5 | $0.00005 | $0.00424 |
| Sonnet 5 | $0.00002 | $0.00169 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
update-python-version 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Python Version Command
You are tasked with updating the minimum Python version requirement across the entire codebase.
Input
The user will provide the new minimum Python version in the format "3.X" (e.g., "3.14", "3.15").
Steps to Execute
1. Validate Input
- Ensure the provided version is in the correct format (e.g., "3.14")
- Extract the old version from
pyproject.tomlby reading therequires-pythonfield
2. Search for All References
Search for all occurrences of the old Python version across the codebase. You must check at the very least:
pyproject.toml-requires-pythonfield.readthedocs.yml- Python version specification.github/workflows/*.yaml- Python version matrices and specificationsREADME.md- Badge and requirements sectionsdocs/index.md- Badge and requirements sectionsdocs/getting-started/installation.md- Requirements sectiondocs/contributing/setup.md- Prerequisites sectiondocs/contributing/architecture.md- Type hints referencesCLAUDE.md- Any version references
Use Grep to search for patterns like:
- The old version number (e.g., "3.13")
- Badge URLs containing the version (e.g., "python-3.13%2B")
- Version specifications in YAML files
3. Update All Files
Update ALL occurrences of the old version to the new version:
pyproject.toml
- Update
requires-python = ">=X.Y"to the new version - Update classifier
"Programming Language :: Python :: X.Y"if present - Note: This may trigger
uv.lockregeneration
.readthedocs.yml
- Update
python: "X.Y"to the new version
.github/workflows/*.yaml
- Update Python version matrices (e.g.,
python-version: ["X.Y", ...]) - Add new version, potentially remove old unsupported versions
Documentation Files
- Update badges from
python-X.Y%2Btopython-X.Z%2B - Update requirements text from "Python X.Y or higher" to "Python X.Z or higher"
- Update any other references (e.g., "(3.Y+)" to "(3.Z+)")
4. Regenerate Lock File
After updating pyproject.toml, regenerate the lock file:
uv sync --all-extras --group dev --group test --group docs
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.
- 2d ago First seen · 104 lines · 11 tokens per session scan A 9ae83687baf9
update-python-version is a command published in the GitHub repository flz/iaqualink-py (44 stars, last pushed 6d ago), licensed BSD-3-Clause. It adds 11 tokens to every session and 847 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.