Amarok-Hider is an Android privacy tool that makes selected files and apps less visible by changing how the system identifies or displays them, rather than encrypting their contents. It is for people who want quick protection from casual snooping, with optional root-based features for deeper app hiding.
Borrowing it
Nothing to install: this file belongs to deltazefiro/Amarok-Hider. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/deltazefiro/Amarok-Hider/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/deltazefiro/Amarok-HiderWrote 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/skills/deltazefiro/amarok-hider/release)<a href="https://agentmods.dev/skills/deltazefiro/amarok-hider/release"><img src="https://agentmods.dev/badge/skills/deltazefiro/amarok-hider/release/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/skills/deltazefiro/amarok-hider/release"><img src="https://agentmods.dev/badge/skills/deltazefiro/amarok-hider/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00015 | $0.01625 |
| Opus 5.5 | $0.00006 | $0.00650 |
| Sonnet 5.5 | $0.00003 | $0.00325 |
| Haiku 4.5 | $0.00002 | $0.00162 |
Grade A, and why
release 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 2mo 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Amarok Release Procedure
You are preparing a new release for Amarok. Follow the steps below in order, asking for user confirmation at each decision point. Do not skip steps.
Step 1: Determine release type and version
- Find the current version in
app/build.gradle(versionCodeandversionName). - Read
git logsince the last tag to understand what changed. - Ask the user: stable or beta? Present both options with their proposed version name and code:
- Stable: use the versioning rules below to propose a version.
- Beta: use the versioning rules below to propose a version.
- Versioning rules for computing the proposed version:
- First beta of new cycle: bump minor version from the current stable (e.g.,
0.10.0→0.11.0-beta1), round versionCode up to next multiple of 10 (e.g.,124→130). - Subsequent beta: increment beta number (e.g.,
-beta1→-beta2), increment versionCode by 1. - Stable release (from beta): drop the beta suffix, increment versionCode by 1.
- Stable patch release: bump patch version (e.g.,
0.10.0→0.10.1), increment versionCode by 1.
- First beta of new cycle: bump minor version from the current stable (e.g.,
Step 2: Merge open translation PRs (stable releases only)
For stable releases only:
- List open PRs from the Weblate bot using:
GITHUB_TOKEN=<token> gh pr list -R deltazefiro/Amarok-Hider --search "translation" - If translation PRs exist, show them to the user.
- IMPORTANT: Tell the user to merge the selected PRs on GitHub directly (using squash merge), then wait for them to confirm. Do NOT merge locally — GitHub's squash merge preserves the correct commit message format with per-language
(by Name <email>)lines that the translation credit script depends on. - After user confirms the PRs are merged on GitHub, run
git pull origin mainto pull them in. - If no translation PRs are found, inform the user and move on.
Step 3: Verify prerequisites
- Confirm git working tree is clean (
git status --shortshould be empty). If not, ask user to resolve. - Build the app:
./gradlew assemble(timeout 300s). If it fails, stop and report the error.
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.
- 2mo ago First seen · 138 lines · 15 tokens per session scan A d4553522e303
release is a skill published in the GitHub repository deltazefiro/Amarok-Hider (3,310 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 1,625 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
release-kotlin-library
Use when preparing, publishing, or checking readiness for a Kotlin library release, including verifying its gradle-maven-publish-plugin prerequisite, reconciling changelogs and API snapshots, and checking publication.
release-new-version
Use when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and publishing to GitHub (main repo, optionally the Xposed repo).
manage-prs
Create, review, and merge GitHub pull requests and publish releases using repository Git rules. Use for requests to open a PR, push and create a PR, review PRs, merge a PR, or tag a release and write release notes.
release-manager
Automated release management skill for uiautomator2-mcp-server. Evaluates codebase status, runs checks, updates documentation, and manages the complete release workflow.
release-process
Step-by-step release checklist for Squad — prevents v0.8.22-style disasters.
gplay-release-flow
Ship Android releases through Google Play with gplay releases. Use when uploading an AAB or APK to a track, promoting a build up the track ladder, steering a staged rollout, inspecting or downloading what a track holds, attaching a ProGuard/R8 mapping, sharing a build via Internal App Sharing, or managing legacy OBB…