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-hardening)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/mobile-hardening"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/mobile-hardening/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-hardening"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/mobile-hardening.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.00038 | $0.00912 |
| Opus 5.5 | $0.00015 | $0.00365 |
| Sonnet 5.5 | $0.00008 | $0.00182 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
mobile-hardening 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mobile-hardening
Generate a platform-specific hardening checklist for an Android or iOS application, covering data storage, network security, binary protections, and anti-tampering.
Trigger
Use before releasing a mobile application to production, or when preparing a security hardening plan for an existing application. Particularly valuable for:
- Pre-release security hardening pass
- Responding to a penetration test report with hardening recommendations
- Upgrading an application from MASVS-L1 to MASVS-L2
- Adding resilience controls for apps with client-side IP protection needs
Input
- Platform: Android or iOS (required)
- Language/Framework: Kotlin, Java, Swift, Objective-C, React Native, Flutter
- Risk profile: Financial/banking, healthcare, enterprise, general consumer
- Current state: What security controls are already in place (if known)
- Target MASVS level: L1 (baseline), L2 (defense-in-depth), L2+R (with resilience)
- Specific concerns: Any particular areas of focus
Process
-
Determine hardening scope based on platform, risk profile, and target MASVS level
-
Generate data storage hardening checklist:
- Migrate sensitive data to platform secure storage
- Configure backup exclusions (android:allowBackup="false", excluded files on iOS)
- Disable screenshot capture for sensitive screens
- Clear clipboard on app background/foreground transitions
- Configure logging to exclude sensitive data in release builds
- Implement proper file permissions for app-created files
-
Generate network security hardening checklist:
- Configure minimum TLS version (1.2+, prefer 1.3)
- Implement certificate pinning (with backup pins and rotation plan)
- Remove cleartext traffic exceptions
- Configure ATS (iOS) or Network Security Config (Android)
- Implement proper certificate validation in custom handlers
-
Generate authentication hardening checklist:
- Bind biometric authentication to cryptographic operations
- Implement secure session management with proper token storage
- Add step-up authentication for sensitive operations
- Configure auto-lock timeout for sensitive apps
- Implement device binding where appropriate
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 · +38 tokens per session a5dbfa731f54
- 1mo ago First seen · 102 lines · 0 tokens per session scan A 4e63ffe2565b
mobile-hardening is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 38 tokens to every session and 912 once invoked, about $0.0002 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.