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/denyszhak/pystack-skills/python-stdlib-idiomsnpx skills add denyszhak/pystack-skills --skill python-stdlib-idiomsgit clone --depth 1 https://github.com/denyszhak/pystack-skillsWhat 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.00174 | $0.02814 |
| Opus 5 | $0.00087 | $0.01407 |
| Sonnet 5 | $0.00035 | $0.00563 |
| Haiku 4.5 | $0.00017 | $0.00281 |
Grade A, and why
python-stdlib-idioms 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 yesterday.
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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stdlib idioms — iteration and tree composition
Two common-but-distinct Python data idioms that don't fit the typing-idioms or value-objects skills, bundled here because each on its own is too thin to be a standalone skill. Use the section that matches your task.
- Iteration — generators,
itertools, lazy pipelines, async iteration - Tree composition — modeling leaf/composite structures with
Protocol+ dataclass, recursive traversal
When to use this skill
- Writing any
for ... in ...loop - Producing a sequence of values lazily
- Composing transformations on a stream
- Iterating async results from a DB query, HTTP stream, message queue
- Modeling a filesystem, expression tree, AST, UI tree
- Building a query DSL where conditions combine (
A AND (B OR C)) - Implementing the visitor pattern on a tree
Part 1 — Iteration
The GoF Iterator pattern exists for languages without first-class iteration. Python has had the iterator protocol (__iter__ / __next__), generators, and itertools since 2.2. There is almost never a reason to write a class with __next__ by hand.
1. Generators over hand-rolled iterators
# Good — three lines, all the iterator machinery is implicit
def line_numbers(lines: Iterable[str]) -> Iterator[tuple[int, str]]:
for i, line in enumerate(lines, start=1):
yield i, line
# Bad — implementing the protocol when generators would do it
class LineNumberIterator:
def __init__(self, lines: Iterable[str]) -> None:
self._lines = iter(lines)
self._i = 0
def __iter__(self) -> "LineNumberIterator":
return self
def __next__(self) -> tuple[int, str]:
self._i += 1
return self._i, next(self._lines)
Generators are the iterator protocol with the right defaults. yield makes a function pause and resume; the generator object handles __iter__, __next__, StopIteration, and send/throw for free.
2. itertools for stream composition
from itertools import chain, groupby, islice, takewhile, pairwise
combined = chain(orders_today, orders_yesterday) # concatenate lazily
first_100 = islice(big_iter, 100) # first 100 only
for status, group in groupby(orders, key=lambda o: o.status):
print(status, list(group)) # consecutive runs by key
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.
- yesterday First seen · 316 lines · 174 tokens per session scan A 6d954f0e4b9c
python-stdlib-idioms is a skill published in the GitHub repository denyszhak/pystack-skills (4 stars, last pushed 3mo ago), licensed MIT. It adds 174 tokens to every session and 2,814 once invoked, about $0.0009 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…