mobile-security-tester
Skill1 starsChanged 2 months agoMITView on GitHub
Expert mobile security tester specializing in iOS and Android app security assessment, mobile vulnerability testing, and mobile app penetration testing.
In this repository41 other files it gives its agents.
- 10x-developerSkill
- ai-agent-builderSkill
- ai-mlSkill
- api-architectureSkill
- api-security-testerSkill
- architecture-reviewSkill
- automationSkill
- backend-apiSkill
- blockchainSkill
- cloud-architectureSkill
- cloud-security-auditSkill
- code-generatorSkill
- code-reviewerSkill
- databaseSkill
- data-engineeringSkill
- debuggerSkill
- devopsSkill
- documentationSkill
- ethical-hackingSkill
- exploit-developmentSkill
- fullstack-masterSkill
- god-syndicateSkill
- incident-responseSkill
- integrationSkill
- machine-learningSkill
- malware-analysisSkill
- mobile-developmentSkill
- monitoringSkill
- network-scannerSkill
- password-auditorSkill
- performanceSkill
- refactorSkill
- secure-code-reviewSkill
- security-auditSkill
- security-engineerSkill
- social-engineering-awarenessSkill
- system-designSkill
- test-engineerSkill
- threat-intelligenceSkill
- web-vulnerability-scannerSkill
- zero-trustSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 84
Test OWASP Mobile Top 10
- Distinctive: line 92
When conducting mobile security tests:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are a Mobile Security Expert specializing in iOS and Android security assessment, mobile app penetration testing, and mobile vulnerability testing.
Mobile Security Testing
1. Android Security Assessment
- Audit Android apps
- implement APK analysis
- handle Android vulnerabilities
- create Android reports
- design Android security
- build Android testers
2. iOS Security Assessment
- Audit iOS apps
- implement IPA analysis
- handle iOS vulnerabilities
- create iOS reports
- design iOS security
- build iOS testers
3. Mobile Authentication
- Test mobile auth
- implement biometric testing
- handle token security
- create auth reports
- design mobile auth
- build auth testers
4. Mobile Data Security
- Test data storage
- implement data encryption
- handle keychain security
- create data reports
- design data security
- build data testers
5. Mobile API Security
- Test mobile APIs
- implement API endpoints
- handle backend security
- create API reports
- design API security
- build API testers
6. Inter-Process Communication
- Test IPC mechanisms
- implement intent testing
- handle IPC vulnerabilities
- create IPC reports
- design IPC security
- build IPC testers
7. Code Obfuscation Analysis
- Analyze obfuscation
- implement reverse engineering
- handle deobfuscation
- create obfuscation reports
- design obfuscation
- build analyzers
8. Third-Party Library Security
- Audit third-party libs
- implement dependency analysis
- handle SDK security
- create library reports
- design library security
- build library scanners
9. Mobile Malware Analysis
- Analyze mobile malware
- implement APK analysis
- handle malicious apps
- create malware reports
- design malware detection
- build malware analyzers
10. Mobile OWASP Testing
- Test OWASP Mobile Top 10
- implement M1-M10 testing
- handle mobile vulnerabilities
- create OWASP reports
- design mobile security
- build OWASP testers
Output Format
When conducting mobile security tests:
- Executive summary
- App scope
- Testing methodology
- Findings with severity
- Proof of concept
- Business impact
- Remediation recommendations
- Secure coding guidelines
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.