axiom audit energy

Security Community

Skill notes

Tool Use Is Mandatory

Run every Glob, Grep, and Read this prompt lists. Do not reason from training data instead of scanning. Run each Grep pattern as written; do not collapse them into one mega-regex. Run the Read verifications each section calls for. "Build a mental model" / "map the architecture" means with tool output in hand, not from memory.

Files to Exclude

Skip: *Tests.swift, *Previews.swift, */Pods/*, */Carthage/*, */.build/*, */DerivedData/*, */scratch/*, */docs/*, */.claude/*, */.claude-plugin/*

Step 3: Identify Power-Intensive Features

Read 2-3 key files to understand: What features use location services? Are they always-on or on-demand? What triggers network requests? User action, timer, or push notification? Are there animations or GPU effects that run continuously? What's the audio/video session lifecycle?

Output

Write a brief Energy Profile Map (8-10 lines) summarizing: Background modes registered and their apparent usage Timer/periodic work count and purpose Location services usage pattern (continuous vs on-demand) Network request trigger pattern (user-driven vs periodic)

Phase 2: Detect Known Anti-Patterns

Run all 8 existing detection categories. For every grep match, use Read to verify the surrounding context before reporting — grep patterns have high recall but need contextual verification.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@CharlesWiltgen · MIT
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Map App Lifecycle and Background Behavior

Phase 1: Map App Lifecycle and Background Behavior

02
Step 1: Identify Background Activity

Step 1: Identify Background Activity

03
Step 2: Identify Periodic Work

Step 2: Identify Periodic Work

04
Step 3: Identify Power-Intensive Features

Read 2-3 key files to understand: What features use location services? Are they always-on or on-demand? What triggers network requests? User action, timer, or push notification? Are there animations or GPU effects that run continuously? What's the audio/video session lifecycle?

05
Phase 2: Detect Known Anti-Patterns

Run all 8 existing detection categories. For every grep match, use Read to verify the surrounding context before reporting — grep patterns have high recall but need contextual verification.

06
Phase 3: Reason About Energy Completeness

Using the Energy Profile Map from Phase 1 and your domain knowledge, check for *unnecessary work* — features consuming power when they shouldn't be active. Question · What it detects · Why it matters Are timers running when the feature they support is inactive? (e.g., refresh timer when the relevant screen isn't visible) · Timers not tied to feature lifecycle · A sync timer running while the user is on a different tab wastes 100% of that energy

07
Phase 4: Cross-Reference Findings

Bump severity for these combinations: Finding A · + Finding B · = Compound · Severity Timer without tolerance · High frequency (<1s interval) · CPU never sleeps · CRITICAL Polling network requests · On cellular without constraints · Radio stays permanently awake · CRITICAL Continuous location · In background mode · GPS drains battery even when app not visible · CRITICAL

08
Phase 5: Energy Health Score

Scoring: EFFICIENT: No CRITICAL issues, all timers have tolerance, location starts match stops, no unnecessary background modes, estimated <2% idle drain above baseline WASTEFUL: No CRITICAL issues, but some timers without tolerance, or unused background modes, or network batching opportunities missed DRAINING: Any CRITICAL issues, or continuous location without stop, or polling without push alternative, or estimated >5% idle drain above baseline

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.