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.
git clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/hermeticormus/libresecops-claude-code/mobile-sec-audit)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/mobile-sec-audit"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/mobile-sec-audit/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/commands/hermeticormus/libresecops-claude-code/mobile-sec-audit"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/mobile-sec-audit.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.01190 |
| Opus 5.5 | $0.00008 | $0.00476 |
| Sonnet 5.5 | $0.00004 | $0.00238 |
| Haiku 4.5 | $0.00002 | $0.00119 |
Grade A, and why
mobile-sec-audit 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 12d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mobile-sec-audit
Structured security audit of a mobile application against OWASP MASVS categories, producing prioritized findings with platform-specific remediation.
Trigger
Use when you need to assess the security posture of an Android or iOS application. Appropriate for:
- Pre-release security assessment
- Periodic security review of existing apps
- Compliance verification against MASVS
- Due diligence on acquired or third-party applications
- Post-incident review of a mobile application
Input
Provide as much of the following as available:
- Platform: Android, iOS, or cross-platform (React Native, Flutter, Xamarin)
- Application purpose: What the app does, what data it handles
- Risk profile: Financial, healthcare, general consumer, enterprise
- Source code or decompiled code (preferred for deep review)
- APK/IPA file information (package name, permissions, manifest)
- Architecture description: Backend API, authentication method, third-party services
- AndroidManifest.xml or Info.plist contents
- Network Security Config (Android) or ATS configuration (iOS)
- Previous assessment results if this is a reassessment
At minimum, provide the platform and application purpose. More context enables more specific findings.
Process
The audit follows OWASP MASVS v2.0 control groups systematically:
-
MASVS-STORAGE -- Data Storage and Privacy
- Review local storage mechanisms (databases, preferences, files)
- Check for sensitive data in logs, clipboard, backups, screenshots
- Verify proper use of platform secure storage (Keystore/Keychain)
- Test data exposure through IPC mechanisms
- Assess third-party analytics/crash reporting data leakage
-
MASVS-CRYPTO -- Cryptography
- Verify algorithm selection (no MD5, SHA-1, DES, RC4, ECB mode)
- Check key generation (proper entropy, platform CSPRNG)
- Assess key storage (hardware-backed Keystore/Secure Enclave)
- Review crypto implementation for common pitfalls (static IVs, key reuse)
- Verify certificate validation in custom TrustManagers/URLSession delegates
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.
- 12d ago Changed · +5 lines · +20 tokens per session 60ace0027bbc
- 1mo ago First seen · 125 lines · 0 tokens per session scan A 382813385189
mobile-sec-audit is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 20 tokens to every session and 1,190 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-09-03.
Other commands, from other repositories
mobile-performance-check
Analyze mobile app for performance issues using the mobile-best-practices database.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.