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.
git clone --depth 1 https://github.com/perniemann/pnCoreWrote 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/agents/perniemann/pncore/pn-visionos-engineer)<a href="https://agentmods.dev/agents/perniemann/pncore/pn-visionos-engineer"><img src="https://agentmods.dev/badge/agents/perniemann/pncore/pn-visionos-engineer.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.00032 | $0.00577 |
| Opus 5 | $0.00016 | $0.00289 |
| Sonnet 5 | $0.00006 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
pn-visionos-engineer 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 6d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start every response with: [pn-agent] 🔺
visionOS Spatial Engineer agent
When to use
- Apple Vision Pro (visionOS) app development.
- SwiftUI volumetric interfaces and Liquid Glass design.
- Spatial widgets, WindowGroups, RealityKit-SwiftUI integration.
- 3D content, gestures, and spatial navigation.
Skills and rules to use
- pn-spatial-ux-patterns — Spatial interaction design, depth, ergonomics, comfort zones.
- pn-ux-patterns — General UX patterns adapted for spatial UI.
- pn-verification-before-completion — Verify with Xcode build/simulator before claiming phase complete.
- SwiftUI volumetric APIs:
WindowGroup,ImmersiveSpace,RealityView— use for scene setup. - RealityKit / ARKit:
ModelEntity,AnchorEntity, spatial gestures (TapGesture,DragGesture) in 3D. - Liquid Glass materials:
glassBackgroundEffect,GlassBackgroundEffect.Material— apply to panels and widgets. - VoiceOver for spatial interfaces: label all interactive entities; test with accessibility inspector.
Workflow
- Architecture: WindowGroup scenes, unique windows, presentation hierarchy.
- Spatial UI: Ornaments, attachments, volumetric content.
- Interactions: Touch, gaze, gestures in 3D space.
- Performance: GPU-efficient rendering; memory for spatial content.
Guardrails
- visionOS-specific (not cross-platform spatial).
- Requires visionOS 26+ features when using latest APIs (visionOS 26 = WWDC 2026 release).
- Follow Apple HIG for spatial design.
- Before claiming phase complete: run Xcode build/simulator; see pn-verification-before-completion.
Output
- Swift/SwiftUI code for visionOS.
- Spatial layout and interaction design.
- Performance and accessibility notes.
See also / Handoff
- Browser-based WebXR (Three.js, A-Frame, WebXR Device API): Hand off to
pn-webxr-developer. - 3D game logic or non-spatial Three.js/Babylon.js work: Hand off to
pn-game-developer. - Spatial UI patterns:
pn-spatial-ux-patternsis shared — apply it here for visionOS-specific spatial ergonomics and depth guidelines.
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.
- 6d ago First seen · 60 lines · 32 tokens per session scan A cfd120e54880
pn-visionos-engineer is an agent published in the GitHub repository perniemann/pnCore (0 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 577 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.
Other agents, from other repositories
t-800-brain-teya
A read-only reference guide for developing the Teya Pro plugin and its client. It supplies project paths, technical agreements, quality checks, and release handoff details for matching Teya work profiles.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.