cpython-runtime-test-run

A procedure for running CinderX and CPython runtime and integration tests. Runtime tests check program behavior, while integration tests check how connected parts work together.

In plain words
What is it for?
Use it for smoke checks, affected test subsets, failed-test reruns, or broad RuntimeTests and CinderX/lib test validation before reporting results.
Why use it?
It separates correctness testing from performance testing and preserves the commands, environment, failures, and reasons for rerunning tests.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/sisibeloved/cpython-optimize-skill/cpython-runtime-test-run
Any agent
npx skills add sisibeloved/cpython-optimize-skill --skill cpython-runtime-test-run
Clone the repo
git clone --depth 1 https://github.com/sisibeloved/cpython-optimize-skill

Made for: Claude Code, Codex.

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 552 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00047 $0.00552
Opus 5 $0.00023 $0.00276
Sonnet 5 $0.00009 $0.00110
Haiku 4.5 $0.00005 $0.00055

Measured yesterday against content hash fe07793a45b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cpython-runtime-test-run 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.

plugins/cpython-optimize-skill/skills/cpython-runtime-test-run/SKILL.md · 38 lines

What it actually says

CPython Runtime Test Run

负责 RuntimeTests 功能测试和 test_cinderx/lib test 集成测试,不负责 pyperformance 性能测试。

三类测试用语

  • RuntimeTests = 功能测试。
  • test_cinderx/lib test = 集成测试。
  • pyperformance = 性能测试,交给 pyperformance-worker-runpyperformance-suite-run

验证等级

  • L1 smoke:import cinderx、最小 JIT、目标单元测试、目标功能测试。
  • L3 相关子集:受影响 RuntimeTests 功能测试、test_cinderx/lib test 集成测试、失败用例集合。
  • L4 全量:近千条 CPython Runtime / CinderX 聚合测试,提交或报告前使用。

命令形态

  • RuntimeTests 功能测试:$CINDERX_TEST_PYTHON ci_pipeline/run_gate.py --suite runtime [--coverage]
  • test_cinderx/lib test 集成测试:CINDERX_LOCAL_RUN_LIBTEST=1 $CINDERX_TEST_PYTHON ci_pipeline/run_gate.py --suite cinderx_local
  • 只跑受影响集合时,保留同一解释器、同一容器线、同一 JIT flags,并记录裁剪理由。

规则

  • L1 未过,不讨论性能收益。
  • 失败重跑必须复用原命令、环境变量、日志路径和 exit status。
  • SIGSEGV / exit 139cinderx-gdb-core-triage
  • AArch64 上出现 DetectsThreadStateOffset 失败、tstate_offset = -1_PyThreadState_GetCurrent@pltTLSDESC 时,先转 cinderx-env-validate / cinderx-env-bootstrap 检查 /opt/python314 是否错误构建为共享/PIC Python;不要先归因到 AutoJIT 新代码。
  • 测试前后记录 Python、CinderX commit、容器线和 JIT flags。
  • 功能测试或集成测试未通过时,不把 pyperformance 性能测试结果写成可提交结论。

输出测试范围、真实命令、失败列表、晋级理由和下一步。

Changes

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.

  1. yesterday First seen · 38 lines · 47 tokens per session scan A fe07793a45b3

Subscribe to this mod's changes

cpython-runtime-test-run is a skill published in the GitHub repository sisibeloved/cpython-optimize-skill (2 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 552 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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…

openai/codex · 114 tokens

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…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 170 tokens