Amethyst is an Android client for Nostr, a social network protocol that lets people control their own social activity and connections. People use it to read and publish Nostr content, follow accounts, and exchange encrypted direct messages from Android and other supported platforms. The catalogue add-ons support workflows for developing or operating the client.
Borrowing it
Nothing to install: this file belongs to vitorpamplona/amethyst. 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/vitorpamplona/amethyst/main/.claude/commands/desktop-run.mdgit clone --depth 1 https://github.com/vitorpamplona/amethystWrote 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/commands/vitorpamplona/amethyst/desktop-run)<a href="https://agentmods.dev/commands/vitorpamplona/amethyst/desktop-run"><img src="https://agentmods.dev/badge/commands/vitorpamplona/amethyst/desktop-run.svg" alt="Measured on agentmods" 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.00006 | $0.00252 |
| Opus 5 | $0.00003 | $0.00126 |
| Sonnet 5 | $0.00001 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
desktop-run 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 8d 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
Build and run the Amethyst Desktop application:
./gradlew :desktopApp:run
Troubleshooting
If the build fails, check:
-
JDK Version: Requires JDK 21+ (
jvmToolchain(21)indesktopApp/build.gradle.kts)java -version -
Compose Multiplatform Plugin: Verify version in
gradle/libs.versions.toml -
Quartz Build: Ensure Quartz compiles first
./gradlew :quartz:build -
Desktop Dependencies: Check
desktopApp/build.gradle.ktshas:implementation(compose.desktop.currentOs)
Creating Distributable
# macOS
./gradlew :desktopApp:packageDmg
# Windows
./gradlew :desktopApp:packageMsi
# Linux
./gradlew :desktopApp:packageDeb # or :desktopApp:packageRpm
Outputs will be in desktopApp/build/compose/binaries/main/
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.
- 8d ago First seen · 46 lines · 6 tokens per session scan A 78440c361c51
desktop-run is a command published in the GitHub repository vitorpamplona/amethyst (1,595 stars, last pushed today), licensed MIT. It adds 6 tokens to every session and 252 once invoked, about $0.0000 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 commands, from other repositories
test-feature
Generate comprehensive tests for a KMP feature.
review-feature
Review a KMP feature against architecture patterns and spec.
health-report
Show health status for all feature modules.
feature-learn
View and manage patterns learned from feature builds. Shows extracted instincts, confidence scores, and feature completeness history.
feature-build
Build a complete mobile feature from description to running code with E2E tests. Orchestrates 6 phases - planning, implementation, testing, build-fix, quality gate, and verification. Auto-detects platform.
feature-status
Show the current status of a feature build - which phase is active, what has completed, what remains, and any blockers.