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-remote-cinderx-lab-setupnpx skills add sisibeloved/cpython-optimize-skill --skill workflow-remote-cinderx-lab-setupgit clone --depth 1 https://github.com/sisibeloved/cpython-optimize-skillWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sisibeloved/cpython-optimize-skill/workflow-remote-cinderx-lab-setup)<a href="https://agentmods.dev/skills/sisibeloved/cpython-optimize-skill/workflow-remote-cinderx-lab-setup"><img src="https://agentmods.dev/badge/skills/sisibeloved/cpython-optimize-skill/workflow-remote-cinderx-lab-setup.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00057 | $0.00290 |
| Opus 5 | $0.00028 | $0.00145 |
| Sonnet 5 | $0.00011 | $0.00058 |
| Haiku 4.5 | $0.00006 | $0.00029 |
Grade A, and why
workflow-remote-cinderx-lab-setup 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 4d 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
Remote CinderX Lab Setup Workflow
定位
Supporting Workflow：环境准备子流程。不要作为端到端优化任务的默认入口；由主 Workflow 调用。
Agent 分派
| 阶段 | Agent | 技能 |
|---|---|---|
| 环境三态 | cinderx-environment-verifier |
cinderx-env-validate |
| 新环境 | cinderx-environment-verifier |
cinderx-env-bootstrap、cinderx-remote-lab-ops |
| 被破坏环境 | cinderx-environment-verifier |
cinderx-env-clean、cinderx-env-bootstrap |
| smoke | cinderx-environment-verifier |
cinderx-smoke-check |
Gate
返回 reusable、needs_bootstrap 或 needs_clean_bootstrap，并记录 host、workspace、container line、Python、SOABI、patchlevel.h、CinderX commit 和 pyperformance 版本。
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.
- 4d ago First seen · 24 lines · 57 tokens per session scan A f2b5cfa38fb9
workflow-remote-cinderx-lab-setup is a skill published in the GitHub repository sisibeloved/cpython-optimize-skill (2 stars, last pushed 6d ago), licensed MIT. It adds 57 tokens to every session and 290 once invoked, about $0.0003 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…