DensityToggle CLAUDE.md

Project instructions for an app that changes display density on Wear OS smartwatches so phone-sized apps fit a round watch screen. Wear OS is Google's smartwatch operating system.

In plain words
What is it for?
Use them when changing the Galaxy Watch Ultra app's automatic density behavior, per-app settings, or handling of phone apps such as YouTube, Uber, Bitwarden, and Proton.
Why use it?
Apps designed for phones can overflow a watch's circular display, hiding controls. The instructions describe shrinking the display for selected apps and restoring it afterward.

Instructions file

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.

agentmods
npx agentmods add instructions/channelramble/densitytoggle/claude-md
Clone the repo
git clone --depth 1 https://github.com/channelramble/DensityToggle
Per session 3,642 This file is loaded in full into every session.
When invoked 3,642 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.03642 $0.03642
Opus 5 $0.01821 $0.01821
Sonnet 5 $0.00728 $0.00728
Haiku 4.5 $0.00364 $0.00364

Measured 2d ago against content hash f2455f122a23, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

DensityToggle CLAUDE.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.

CLAUDE.md · 276 lines

How it starts

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

Density Toggle - Wear OS display density control

Context file for Claude Code. Read this before changing anything.

Goal

A Galaxy Watch Ultra (480x480 round, Wear OS / One UI Watch) runs sideloaded phone APKs - YouTube, Uber, Bitwarden, Proton - whose layouts are built for a large rectangular screen. At stock density their UI overflows the round display and controls fall outside the visible circle.

The app lowers system display density so those layouts fit, and puts it back afterwards. Auto-first since v5.9:

  • Auto - an accessibility service that shrinks when a chosen app comes to the foreground and restores when it leaves. Each chosen app can have its own density (default from the main screen, per-app override in the picker) and its own full-size-typing setting (per-app chip in the picker; no global toggle anymore).
  • "Full-size typing" was removed in v5.15 after empirical retesting: the current One UI Watch keyboard works fine at low densities (its numbers/symbols gesture functions at 140), so lifting density while the keyboard was up no longer bought anything and cost a chip + a state machine. If keyboard breakage at low dpi ever returns, the git history has the whole implementation (kbPause/kbPaused/kbLiftFor + KB_SAFE_DPI=190) - re-test on the device before resurrecting it.
  • Reach (v5.12, optional, off by default): corner controls of phone layouts are physically outside the round panel at every density - overscan was removed in Android 11 and One UI Watch's WM coerces freeform back to fullscreen (both verified on-device), so proxy-clicking is the ONLY workaround. The service shows a TYPE_ACCESSIBILITY_OVERLAY chip while a watched app is shrunk; the panel lists clickable nodes whose centre lies outside the inscribed circle and fires ACTION_CLICK on the chosen one. Overlay sizes are PHYSICAL px, never dp - dp shrinks with the density override, exactly when the chip is needed. Useless for unreadable trees (YouTube, invariant 10).
  • The manual shrink workflow was removed in v5.9. The only manual control is a Restore to stock pill that appears while the screen is actually shrunk - the on-watch escape hatch. Do not remove it: without it a stuck shrink needs adb. (v6.0 briefly made it always-visible as "Reset to default"; reverted - it caused layout churn.)
  • Rotation is NOT an in-app feature (v5.10 tried, v5.10.1 removed it - learn from this): shrinking density makes phone apps use tablet layouts, which honour SENSOR orientation, so apps rotate with the wrist. The accelerometer_rotation setting cannot stop sensor-orientation requests, so an in-app toggle built on it LOOKS like it works but doesn't. The mode that works - cmd window fixed-to-user-rotation enabled - is gated by a signature permission the app can never hold, is adb-only, and is persisted by the system across reboots. It lives in install.sh (--lock-rotation) and INSTALL.md. Do not re-add a rotation toggle to the app.

Read the full file on GitHub · 276 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. 2d ago First seen · 276 lines · 3,642 tokens per session scan A f2455f122a23

Subscribe to this mod's changes

DensityToggle CLAUDE.md is an instructions file published in the GitHub repository channelramble/DensityToggle (24 stars, last pushed 18d ago), licensed MIT. It adds 3,642 tokens to every session, about $0.0182 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.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens