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 rules/deltazefiro/amarok-hider/prototypegit clone --depth 1 https://github.com/deltazefiro/Amarok-HiderWhat 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.00012 | $0.00111 |
| Opus 5 | $0.00006 | $0.00056 |
| Sonnet 5 | $0.00002 | $0.00022 |
| Haiku 4.5 | $0.00001 | $0.00011 |
Grade A, and why
prototype 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.
What it actually says
Prototype Guidelines
- Use
debugPrefinui/settings/AboutCategory.javaas your prototype entry point:- For feature testing: Trigger your new code when
debugPrefis clicked - For UI testing: Launch your test view when
debugPrefis clicked
- For feature testing: Trigger your new code when
- Use
R.drawable.ic_nullinstead of creating new drawable assets - Keep changes minimal and prefer adding new code over modifying existing code
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 · 11 lines · 12 tokens per session scan A 701a9471250b
prototype is a cursor rule published in the GitHub repository deltazefiro/Amarok-Hider (3,222 stars, last pushed 22d ago), licensed Apache-2.0. It adds 12 tokens to every session and 111 once invoked, about $0.0001 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.
Other cursor rules, from other repositories
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
security-threat-and-stability
Maximum security scrutiny on issues/PRs and stability-first code changes.
data-layer
Data layer rules: Room, DataStore, networking, offline-first, Paging 3, serialization.
android-compose-foundations
Build Android UI with Jetpack Compose foundations, layouts, modifiers, theming, and stable component structure.
android-gradle-build-logic
Shape Android build logic with Gradle, version catalogs, plugins, convention patterns, and toolchain compatibility.
android-kotlin-core
Use Kotlin idioms safely in Android apps, including nullability, data classes, sealed types, extension functions, and collection pipelines.