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 instructions/ackeskin/contexture/openxrgit clone --depth 1 https://github.com/AcKeskin/contextureWhat 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.02128 | $0.02128 |
| Opus 5 | $0.01064 | $0.01064 |
| Sonnet 5 | $0.00426 | $0.00426 |
| Haiku 4.5 | $0.00213 | $0.00213 |
Grade A, and why
contexture openxr.instructions.md 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
openxr rules
Auto-loaded by Copilot when editing files matching
**. Generated fromarchitectural-rules/openxr/— do not hand-edit.
OpenXR extensions and portability
Call xrEnumerateInstanceExtensionProperties before constructing XrInstanceCreateInfo::enabledExtensionNames. Never pass extension names that have not been confirmed present; xrCreateInstance will return XR_ERROR_EXTENSION_NOT_PRESENT and fail. (OpenXR: xrEnumerateInstanceExtensionProperties, XrInstanceCreateInfo, XR_ERROR_EXTENSION_NOT_PRESENT)
Partition extensions into required (app cannot function without them — abort if absent) and optional (enhanced experience — feature-gate at runtime). Document this split explicitly in the extension query phase. This is the primary portability seam across runtimes. (OpenXR: xrEnumerateInstanceExtensionProperties)
Do not call functions or use structures from an optional extension unless that extension was successfully enabled. Extension functions obtained via xrGetInstanceProcAddr are null when the extension is absent; calling them is undefined behaviour. (OpenXR: xrGetInstanceProcAddr)
Load all extension function pointers via xrGetInstanceProcAddr after instance creation. Do not link extension entry points statically where the loader may not expose them. (OpenXR: xrGetInstanceProcAddr)
Enumerate API layers with xrEnumerateApiLayerProperties in debug/development builds; enable validation layer (XR_APILAYER_LUNARG_core_validation) when available. Never hard-enable a layer in release builds — the layer may be absent on end-user machines and will cause instance creation failure. (OpenXR: xrEnumerateApiLayerProperties, XrInstanceCreateInfo::enabledApiLayerNames)
Check the XrResult of every OpenXR call. Many functions return XR_SUCCESS for the normal case but XR_SESSION_LOSS_PENDING or XR_ERROR_* for recoverable or fatal conditions. Ignoring results silently corrupts frame loop state. Use XR_SUCCEEDED(result) for coarse checks; match specific codes for recoverable paths. (OpenXR: XrResult, XR_SUCCEEDED, XR_SESSION_LOSS_PENDING)
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 · 72 lines · 2,128 tokens per session scan A 5526651fd4a3
contexture openxr.instructions.md is an instructions file published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 2,128 tokens to every session, about $0.0106 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 instructions, from other repositories
skills AGENTS.md
Instructions for CometWorks/skills: You are an experienced developer of Space Engineers in-game scripts, mods, and plugins.
ccjk AGENTS.md
Instructions for miounet11/ccjk, covering repository guidelines, source of truth, behavior, validation and notes.
stenographer-mode copilot-instructions.md
Instructions for AkashAi7/stenographer-mode, covering steno mode — global instructions, contract, rules and levels.
claude-code-tamagotchi CLAUDE.md
Instructions for Ido-Levi/claude-code-tamagotchi, covering claude.md, essential commands, development, run the pet in statusline mode (main entry point) and development mode with auto-reload.
.claude CLAUDE.md
Instructions for travisjneuman/.claude, covering claude.md — global development constitution, identity & role, p0 non-negotiables, optional shared agent operating layer and workflow.
godot-superpowers CLAUDE.md
Instructions for Simone-Tarantino/godot-superpowers, covering claude.md, what this repo is, layout, editing rules for this repo and developing this plugin.