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/skills/find-non-lambda-logs/SKILL.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/skills/vitorpamplona/amethyst/find-non-lambda-logs)<a href="https://agentmods.dev/skills/vitorpamplona/amethyst/find-non-lambda-logs"><img src="https://agentmods.dev/badge/skills/vitorpamplona/amethyst/find-non-lambda-logs.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.00072 | $0.02822 |
| Opus 5 | $0.00036 | $0.01411 |
| Sonnet 5 | $0.00014 | $0.00564 |
| Haiku 4.5 | $0.00007 | $0.00282 |
Grade A, and why
find-non-lambda-logs 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 7d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Non-Lambda Log Calls
Overview
Three related logging hygiene issues:
- Lambda overload missing.
Log.d/i/w/ecalls that use string interpolation without the lambda overload waste string allocation when the log level is filtered out in release builds. - Throwable dropped in catch blocks.
Log.w/ecalls insidecatch (e: ...)blocks that interpolate${e.message}but don't passelose the stack trace, and log nothing useful whene.messageis null (NPE, IOException with no message, etc.). - Still on
android.util.Log. Files importing the platform logger bypassLog.minLeveland theLogSink, and have no lambda overload — so neither fix above can be applied to them. Step 0 finds these; the last section migrates them.
When to Use
- After merging branches that add new logging
- Periodic audit of logging hygiene
- After migrating
android.util.Logusages to the sharedLogwrapper
What to Flag
Calls with string interpolation ($ in message) that do not pass a throwable:
// FLAG - interpolation without lambda, no throwable
Log.d("Tag", "Processing ${event.id}")
Log.w("Tag", "Failed for $url")
// IGNORE - passes throwable (lambda overload doesn't accept throwable)
Log.w("Tag", "Error: ${e.message}", e)
Log.e("Tag", "Failed for $url", throwable)
// IGNORE - no interpolation (no allocation benefit from lambda)
Log.d("Tag", "Initialization complete")
Search Commands
Important: Tags can be string literals ("Tag") or variables (tag, LOG_TAG). Run both patterns for each step.
The throwable-name alternation, used by Steps 2 and 3 — define it once and reuse it, rather than writing a shorter list in one step and a longer one in another:
THROWABLE='(e|t|it|ex|err|error|throwable|cause|tr)'
Filter the noise before counting, or the totals mislead: drop /build/, /androidTest/ and /src/test/ (release filtering doesn't apply to tests), and drop lines whose first non-space character is // or * — commented-out calls and KDoc examples both match these patterns. A grep -vE ':[0-9]+: *(//|\*)' handles the last one.
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.
- 7d ago First seen · 192 lines · 72 tokens per session scan A 7fb8c91ef011
find-non-lambda-logs is a skill published in the GitHub repository vitorpamplona/amethyst (1,595 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 2,822 once invoked, about $0.0004 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 skills, from other repositories
compose-performance
Use when investigating Jetpack Compose recomposition cost, compiler stability reports, skippability, unstable parameters, frame-rate State reads, cross-phase snapshot back-writing, or @ReadOnlyComposable contracts.
context-collector
Deep architecture recovery, context gathering, and root cause analysis for unfamiliar or undocumented codebases. Use when asked to analyze a codebase, understand its architecture, map dependencies, gather context before a task, do architecture recovery, explore an unknown repo, or investigate a production…
mac-ram-cleanup
Diagnose and reduce macOS RAM pressure using kernel telemetry (memory pressure, compressor, swap rates), not fake 'free RAM'. Use whenever the user mentions Mac RAM, memory pressure, swap used, compressed memory, Activity Monitor Memory tab, a sluggish Mac with RAM full, RAM cleaners, sudo purge, kerneltask or…
argent-react-native-optimization
Optimizes a React Native app by profiling first to find real bottlenecks, then sweeping for mechanical issues. Entry-point for all performance work. Use when the app feels slow, user asks to optimize, fix re-renders, reduce jank, or improve startup. Delegates to argent-react-native-profiler for measurement.
sceneview
Build 3D and AR apps with the SceneView SDK in Jetpack Compose, SwiftUI (iOS/macOS/visionOS via SceneViewSwift), Web (Filament.js), Flutter and React Native. Use whenever the user asks for "3D in Compose", "AR with ARCore in Compose", a model viewer, or any cross-platform 3D/AR app where the dependency is…
to-plan
Use when one ready GitHub issue or an in-chat task needs a repository-aware implementation plan for a later implementation workflow.