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/baijum/ukulele-companionWrote 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/rules/baijum/ukulele-companion/edge_to_edge)<a href="https://agentmods.dev/rules/baijum/ukulele-companion/edge_to_edge"><img src="https://agentmods.dev/badge/rules/baijum/ukulele-companion/edge_to_edge/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.
<a href="https://agentmods.dev/rules/baijum/ukulele-companion/edge_to_edge"><img src="https://agentmods.dev/badge/rules/baijum/ukulele-companion/edge_to_edge.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01300 |
| Opus 5.5 | $0.00000 | $0.00520 |
| Sonnet 5.5 | $0.00000 | $0.00260 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
edge_to_edge 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 1mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edge-to-Edge Play Store Warnings (Expected — No Action)
Google Play Console shows two "recommended actions" on every production release. They were first analyzed in March 2026 and re-analyzed in September 2026 against the shipped 9.13.0 release (versionCode 110). Both are expected and require no app change. Do not spend a session re-investigating them unless something in the "Re-check when" section below has changed.
Warning 1: "Edge-to-edge may not display for all users"
- Status: Already handled by app code.
MainActivity.onCreate()callsenableEdgeToEdge()beforesetContent.FretboardScreenandOnboardingScreenuse Material 3ScaffoldwithinnerPadding, which accounts for system bar insets; the onboarding bottom bar appliesnavigationBarsPadding().targetSdkis 36, and no theme or manifest useswindowOptOutEdgeToEdgeEnforcement,statusBarColor,navigationBarColororwindowLayoutInDisplayCutoutMode.- This banner is the generic companion to Warning 2 and fires together with it.
Warning 2: "Your app uses deprecated APIs or parameters for edge-to-edge"
-
Deprecated APIs flagged:
setStatusBarColor,setNavigationBarColor,setDecorFitsSystemWindows,layoutInDisplayCutoutMode, and the status/navigation bar contrast-enforced setters. -
Root cause (verified September 2026): every caller is inside AndroidX, none is app code. Verified by disassembling the release APK (
dexdumpfrom build-tools) and mapping the obfuscated class names throughapp/build/outputs/mapping/release/mapping.txt:Deprecated API Caller in the shipped APK Window.setStatusBarColor/setNavigationBarColorandroidx.activity.EdgeToEdgeApi26,EdgeToEdgeApi29,EdgeToEdgeApi35Window.setDecorFitsSystemWindowsR8-outlined API stub for androidx.core.view.WindowCompatWindowManager.LayoutParams.layoutInDisplayCutoutModeR8-outlined API stub for AndroidX Core setStatusBarContrastEnforced/setNavigationBarContrastEnforcedR8-outlined API stub for AndroidX Compose UI
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.
- 1mo ago Changed · +50 lines 983cc3ef3d47
- 1mo ago First seen · 34 lines · 0 tokens per session scan A 14c77e6d653f
edge_to_edge is a cursor rule published in the GitHub repository baijum/ukulele-companion (14 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,300 tokens. 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 cursor rules, from other repositories
project
Redface 2 project rules — imports AGENTS.md as source of truth.
project-status
PriceGrab shipped state and product backlog (read first).
tune-tangler-project
Tune Tangler — conventions, repo layout, doc links.
git-consent
Git — consent for commits/push; amend; context before risky git ops.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.