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 skills add sechiro/VRCUdonSkills-for-Codex --skill codex-edit-stability-windowsgit clone --depth 1 https://github.com/sechiro/VRCUdonSkills-for-CodexWrote 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/sechiro/vrcudonskills-for-codex/codex-edit-stability-windows)<a href="https://agentmods.dev/skills/sechiro/vrcudonskills-for-codex/codex-edit-stability-windows"><img src="https://agentmods.dev/badge/skills/sechiro/vrcudonskills-for-codex/codex-edit-stability-windows.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.1 | $0.00128 | $0.00778 |
| Opus 5 | $0.00064 | $0.00389 |
| Sonnet 5 | $0.00026 | $0.00156 |
| Haiku 4.5 | $0.00013 | $0.00078 |
Grade A, and why
codex-edit-stability-windows 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 8d 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
Codex Edit Stability Windows
役割
Windows 上での Codex 編集作業を安定させる。特に apply_patch 失敗、PowerShell 由来の文字化け、UTF-8 / BOM 問題、here-string 展開事故を避けるための作業手順を与える。
この Skill を使う場面
- Codex の編集で文字化けが起きやすい
apply_patchが頻繁に失敗する- PowerShell の
Set-Content/ here-string で内容が壊れやすい - 日本語を含む Markdown やテンプレートを安全に編集したい
- 編集後の検証手順を標準化したい
この Skill を使わない場面
- 通常の実装ノウハウだけで十分なとき
- Windows 特有の編集事故を扱わないとき
基本方針
- まず
references/edit-failure-analysis.mdを読む。 - 実編集前に
references/safe-edit-workflow.mdを読む。 - 文字化けしやすいファイルでは、PowerShell の安易な文字列置換より安全な手段を優先する。
apply_patchが通るなら最優先で使う。apply_patchが使えない場合だけ、UTF-8 を明示した安全な書き込みへ切り替える。- 編集後は必ず
references/verification-checklist.mdの確認を行う。
優先する編集手段
apply_patch- 既存の安全なテンプレートコピー
- UTF-8 を明示した最小限のファイル再書き込み
避けるもの
- PowerShell のバッククォート解釈が絡む複雑な置換
- 展開付き here-string 内での Markdown / URL / バッククォート混在
- 文字コードを明示しない
Set-Content - BOM 混入を意識しない C# / YAML 出力
- 編集後未検証のまま完了扱いにすること
典型フロー
- 失敗原因が
apply_patchか文字化けかを切り分ける。 - 対象ファイルが
.cs/.yaml/.mdのどれかを確認する。 apply_patchを試す。- 失敗したら、ファイル種別に応じた安全手段へ切り替える。
- 編集後に、置換文字、BOM、意図しない
?、未解決プレースホルダを確認する。 - その後にステージングや次作業へ進む。
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 56 lines · 128 tokens per session scan A 5fd53c508277
codex-edit-stability-windows is a skill published in the GitHub repository sechiro/VRCUdonSkills-for-Codex (58 stars, last pushed 4mo ago), licensed MIT. It adds 128 tokens to every session and 778 once invoked, about $0.0006 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…