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/sisibeloved/cpython-optimize-skill/workflow-pyperformance-regressionnpx skills add sisibeloved/cpython-optimize-skill --skill workflow-pyperformance-regressiongit clone --depth 1 https://github.com/sisibeloved/cpython-optimize-skillWhat 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.00046 | $0.00565 |
| Opus 5 | $0.00023 | $0.00282 |
| Sonnet 5 | $0.00009 | $0.00113 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
workflow-pyperformance-regression 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.
What it actually says
pyperformance Regression Workflow
定位
Supporting Workflow：正式性能验证分支。由主 Workflow 在 L3/L4 阶段调用。
Agent 分派
| 阶段 | Agent | 技能 |
|---|---|---|
| 环境确认 | cinderx-environment-verifier |
cinderx-env-validate |
| A/B slot | cinderx-orchestrator |
cinderx-ab-run-slot |
| baseline | pyperformance-baseline-runner |
pyperformance-suite-run |
| candidate | pyperformance-candidate-runner |
pyperformance-suite-run |
| 分析 | pyperformance-benchmark-analyst |
pyperformance-result-compare |
| 报告 | pyperformance-benchmark-analyst |
cinderx-optimization-report |
Gate
baseline/candidate 必须说明口径 baseline 和提交 baseline。并行前 CPU set、绑核、结果目录、容器线不冲突。
正式 A/B 前必须引用 ../using-cpython-optimize/references/baseline-source-contract.md，确认 baseline source 是 baseline_source_verified。远程环境或容器可用只能证明执行环境可跑，不能自动把远程 workspace 当前源码当 baseline；若返回 baseline_source_untrusted，先让用户指定 baseline、创建干净 worktree 或重建 cpython-baseline。
正式运行前必须让 baseline/candidate runner 共同引用 ../using-cpython-optimize/references/pyperformance-affinity-guidance.md，确认用户命令里的 --affinity 已按当前 nproc / lscpu / taskset -pc $$ / 容器 cpuset 映射到可用 CPU；不能逐字照抄不可用高核号。
正式运行前必须让 baseline/candidate runner 共同引用 ../using-cpython-optimize/references/pyperformance-env-contract.md，确认 --inherit-environ、driver/worker env、helper 变量和唯一差异轴一致；CinderX JIT 口径还要确认 worker 可见的 .pth、pyvenv.cfg / include-system-site-packages、cinderx.is_initialized() 等证据。环境契约缺失时不能进入正式 pyperf compare_to 结论。
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 · 32 lines · 46 tokens per session scan A c01fc180e642
workflow-pyperformance-regression is a skill published in the GitHub repository sisibeloved/cpython-optimize-skill (2 stars, last pushed 4d ago), licensed MIT. It adds 46 tokens to every session and 565 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…