axiom-display-performance

axiom-display-performance is a skill for Claude Code, Codex from ComeOnOliver/skillshub. It costs 56 tokens per session (4,626 once invoked), scanned A, original, MIT.

A guide to diagnosing frame-rate and animation problems on variable-refresh-rate displays such as Apple's ProMotion screens. It covers render-loop setup, frame pacing, system limits, and measuring actual displayed frames.

In plain words
What is it for?
Use it to investigate frame-rate caps, slow rendering, uneven frame timing, and configuration issues in MTKView, CADisplayLink, or CAMetalDisplayLink.
Why use it?
It helps explain why an app remains at 60 frames per second or stutters even when a faster display is available.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to investigate frame-rate caps, slow rendering, uneven frame timing, and configuration issues in MTKView, CADisplayLink, or CAMetalDisplayLink.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/comeonoliver/skillshub/axiom-display-performance
Install

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.

Any agent
npx skills add ComeOnOliver/skillshub --skill axiom-display-performance
Clone the repo
git clone --depth 1 https://github.com/ComeOnOliver/skillshub

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for axiom-display-performance

README.md
[![agentmods](https://agentmods.dev/badge/skills/comeonoliver/skillshub/axiom-display-performance/github.svg)](https://agentmods.dev/skills/comeonoliver/skillshub/axiom-display-performance)
Your own site
<a href="https://agentmods.dev/skills/comeonoliver/skillshub/axiom-display-performance"><img src="https://agentmods.dev/badge/skills/comeonoliver/skillshub/axiom-display-performance/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for axiom-display-performance

Your own site · 80×15
<a href="https://agentmods.dev/skills/comeonoliver/skillshub/axiom-display-performance"><img src="https://agentmods.dev/badge/skills/comeonoliver/skillshub/axiom-display-performance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,626 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.04626
Opus 5 $0.00028 $0.02313
Sonnet 5 $0.00011 $0.00925
Haiku 4.5 $0.00006 $0.00463

Measured 9d ago against content hash 5e116ac57084, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

axiom-display-performance 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 9d 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.

skills/CharlesWiltgen/Axiom/axiom-display-performance/SKILL.md · 635 lines

How it starts

The opening of the file, as written. The whole thing — 635 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Display Performance

Systematic diagnosis for frame rate issues on variable refresh rate displays (ProMotion, iPad Pro, future devices). Covers render loop configuration, frame pacing, hitch mechanics, and production telemetry.

Key insight: "ProMotion available" does NOT mean your app automatically runs at 120Hz. You must configure it correctly, account for system caps, and ensure proper frame pacing.


Part 1: Why You're Stuck at 60fps

Diagnostic Order

Check these in order when stuck at 60fps on ProMotion:

  1. Info.plist key missing? (iPhone only) → Part 2
  2. Render loop configured for 60? (MTKView defaults, CADisplayLink) → Part 3
  3. System caps enabled? (Low Power Mode, Limit Frame Rate, Thermal) → Part 5
  4. Frame time > 8.33ms? (Can't sustain 120fps) → Part 6
  5. Frame pacing issues? (Micro-stuttering despite good FPS) → Part 7
  6. Measuring wrong thing? (UIScreen vs actual presentation) → Part 9

Part 2: Enabling ProMotion on iPhone

Critical: Core Animation won't access frame rates above 60Hz on iPhone unless you add this key.

<!-- Info.plist -->
<key>CADisableMinimumFrameDurationOnPhone</key>
<true/>

Without this key:

  • Your preferredFrameRateRange hints are ignored above 60Hz
  • Other animations may affect your CADisplayLink callback rate
  • iPad Pro does NOT require this key

When to add: Any iPhone app that needs >60Hz for games, animations, or smooth scrolling.


Part 3: Render Loop Configuration

MTKView Defaults to 60fps

This is the most common cause. MTKView's preferredFramesPerSecond defaults to 60.

// ❌ WRONG: Implicit 60fps (default)
let mtkView = MTKView(frame: frame, device: device)
mtkView.delegate = self
// Running at 60fps even on ProMotion!

// ✅ CORRECT: Explicit 120fps request
let mtkView = MTKView(frame: frame, device: device)
mtkView.preferredFramesPerSecond = 120
mtkView.isPaused = false
mtkView.enableSetNeedsDisplay = false  // Continuous, not on-demand
mtkView.delegate = self

Read the full file on GitHub · 635 lines

Changes

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.

  1. 9d ago First seen · 635 lines · 56 tokens per session scan A 5e116ac57084

Subscribe to this mod's changes

axiom-display-performance is a skill published in the GitHub repository ComeOnOliver/skillshub (63 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 4,626 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-09-03.