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/openai/codex/path-typesnpx skills add openai/codex --skill path-typesgit clone --depth 1 https://github.com/openai/codexWhat 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.00029 | $0.00507 |
| Opus 5 | $0.00015 | $0.00253 |
| Sonnet 5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
path-types 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- path-types — 100% identical, 0 lines differ
- path-types — 100% identical, 0 lines differ
- path-types — 100% identical, 0 lines differ
- path-types — 100% identical, 0 lines differ
- path-types — 100% identical, 0 lines differ
- path-types — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Path Types
Apply this guidance when defining new types. Change existing code only when explicitly requested, and keep edits minimal and proportional. Treat these rules as the target state of an ongoing migration; if compliance is difficult, ask the user how to proceed.
- In app-server protocol types, use
LegacyAppPathStringfor backwards compatibility during the URI migration. At the protocol boundary, convert it toPathUriand usePathUriinternally. For host-local logic, such as some config values, useAbsolutePathBuforPathBufinstead. - In exec-server protocol types, use
PathUri. Internally, usePathUriorAbsolutePathBufas appropriate. - In dependencies shared by both servers, use
PathUrior separate APIs that decouple their use cases. - Tool call arguments that the model is expected to generate should be deserialized as regular
Strings with feature-specific path handling code.
Migration requirements
Keep these requirements in mind while migrating code to conform with the above guidelines:
- existing app-server clients keep sending and receiving legacy native-path strings
- app-server can retain and manipulate foreign-platform path URIs
- exec-server APIs use file:// URIs
- local-only operation must not change model-visible text
- model tool arguments may contain raw relative or absolute paths for any OS
- path reasoning must work before the related environment has come online
- URIs cannot explicitly encode the executor’s path convention or operating system
- users must not configure the environment’s OS/path convention explicitly
- URIs should not yet be stored in rollouts, databases, or other persistent storage
- path conversion errors: fail-closed for security-relevant paths, fail-open for UI/diagnostics
- prefer small focused methods on
PathUriorLegacyAppPathStringover local helpers - represent
PathUrivalues as URIs in diagnostics
It is OK if the conversion between paths and URIs is somewhat lossy as long as it will do the right thing for real users.
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 · 44 lines · 29 tokens per session scan A 890145a2ee66
path-types is a skill published in the GitHub repository openai/codex (120,598 stars, last pushed today), licensed Apache-2.0. It adds 29 tokens to every session and 507 once invoked, about $0.0001 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.
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…
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…
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…
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…
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.