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/stellarshenson/claude-code-plugins/progressbarsnpx skills add stellarshenson/claude-code-plugins --skill progressbarsgit clone --depth 1 https://github.com/stellarshenson/claude-code-pluginsWhat 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.00039 | $0.00831 |
| Opus 5 | $0.00019 | $0.00415 |
| Sonnet 5 | $0.00008 | $0.00166 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
progressbars 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Progress Bars Skill
Progress bars for Python scripts and Jupyter.
Selection Rule
MANDATORY: ASK user which style (classic or modern) before implementing. Never assume.
Quick Reference
Classic (tqdm)
Works everywhere - terminals, Jupyter, IDE. Renders native ipywidgets in Jupyter when ipywidgets installed.
Deps: tqdm, ipywidgets (Jupyter widgets)
Import: from tqdm.auto import tqdm - .auto auto-selects backend.
from tqdm.auto import tqdm
# determinate
for item in tqdm(items, desc="Processing", unit="file"):
process(item)
# with ThreadPoolExecutor
from concurrent.futures import ThreadPoolExecutor, as_completed
with ThreadPoolExecutor(max_workers=16) as executor:
futures = {executor.submit(fn, item): item for item in items}
for future in tqdm(as_completed(futures), total=len(futures), desc="Loading", unit="item"):
result = future.result()
Modern (rich)
Spinners, elapsed time, ETA. Terminals + Jupyter.
Deps: rich
from rich.progress import (
BarColumn, MofNCompleteColumn, Progress,
SpinnerColumn, TextColumn, TimeElapsedColumn,
)
with Progress(
SpinnerColumn(),
TextColumn("[steel_blue]{task.description}"),
BarColumn(bar_width=40),
MofNCompleteColumn(),
TimeElapsedColumn(),
refresh_per_second=10,
) as progress:
task = progress.add_task("Processing", total=len(items))
for item in items:
process(item)
progress.advance(task)
# force completion (prevents N-1 issue)
progress.update(task, completed=len(items))
progress.refresh()
Modern (rich) - Completion Fixes
- N-1 issue (stops one short): common with parallel execution. After loop:
progress.update(task, completed=total)thenprogress.refresh(). Defensive for sequential too - Bar disappears:
transient=Trueclears on context exit.transient=False(default) keeps visible - Stuck below 100%:
total=doesn't matchadvance()count. Advance every iteration, even when skipping - Spinner won't stop: all tasks must reach
completed == total. Verify total matches iteration count - Bar frozen: default refresh 10/sec.
refresh_per_second=10or callprogress.refresh() - Multiple bars overwrite: create tasks before loop, use
progress.reset(task, total=...)per batch
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 · 112 lines · 39 tokens per session scan A e8ff68813c9d
progressbars is a skill published in the GitHub repository stellarshenson/claude-code-plugins (3 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 831 once invoked, about $0.0002 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.