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.
npx agentmods add skills/robertguss/claude-code-toolkit/app-review-analyzernpx skills add robertguss/claude-code-toolkit --skill app-review-analyzergit clone --depth 1 https://github.com/robertguss/claude-code-toolkitWrote 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/robertguss/claude-code-toolkit/app-review-analyzer)<a href="https://agentmods.dev/skills/robertguss/claude-code-toolkit/app-review-analyzer"><img src="https://agentmods.dev/badge/skills/robertguss/claude-code-toolkit/app-review-analyzer.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 | $0.00123 | $0.01397 |
| Opus 5 | $0.00062 | $0.00698 |
| Sonnet 5 | $0.00025 | $0.00279 |
| Haiku 4.5 | $0.00012 | $0.00140 |
Grade A, and why
app-review-analyzer 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 4d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prerequisites
- Chrome browser with Claude in Chrome extension (for reading store reviews)
- No API keys required — all analysis is done through live browser interaction
- Supports iOS App Store and Google Play Store
Mode Selection
Ask the user which mode they need:
- Competitive Analysis — Analyze a competitor's reviews to find gaps and opportunities
- Own App Management — Analyze your own app's reviews to prioritize fixes, surface feature requests, and draft professional responses
If the user provides a competitor's app, use Competitive Analysis mode. If they mention "my app" or "our app," use Own App Management mode.
Competitive Analysis Mode
Step 1: Navigate to the App Listing
Open the app's store page in Chrome:
- iOS App Store: Search on apps.apple.com or use a direct link
- Google Play: Search on play.google.com or use a direct link
Confirm the correct app with the user before proceeding.
Step 2: Collect Reviews Systematically
Read reviews in two passes:
- Most Recent — Sort by newest first. Read at least 30-50 reviews to capture current sentiment.
- Most Critical — Sort by lowest rating (1-star, then 2-star). Read at least 20-30 critical reviews to surface pain points.
For each review, note:
- Star rating
- Date posted
- Review text (key quotes)
- Whether the developer responded
Step 3: Categorize Reviews
Assign each review to one or more theme categories:
| Category | Signals |
|---|---|
| Bug Reports | Crashes, errors, data loss, freezing, sync failures |
| Missing Features | "I wish it had...", "Why can't I...", "Needs..." |
| UX Complaints | "Too complicated", "Can't find...", "Confusing", "Slow" |
| Pricing Objections | "Too expensive", "Not worth it", "Used to be free" |
| Praise | Specific features users love, "best app for...", loyalty signals |
| Support Complaints | "No response", "Unhelpful", "Can't reach anyone" |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 181 lines · 123 tokens per session scan A 70020d5c764d
app-review-analyzer is a skill published in the GitHub repository robertguss/claude-code-toolkit (108 stars, last pushed 27d ago), licensed MIT. It adds 123 tokens to every session and 1,397 once invoked, about $0.0006 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
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
offensive-edr-evasion
EDR evasion offensive checklist: hook unhooking (user/kernel), direct syscalls, PPID spoofing, process injection variants, AMSI bypass, ETW patching, memory encryption, and behavior-based evasion. Use when planning EDR bypass during red team engagements or researching AV/EDR evasion techniques.
offensive-mitigations
Security mitigation reference and bypass catalog: ASLR, DEP/NX, RELRO, stack canaries, CFI, sandboxing, seccomp. Covers both detection of enabled mitigations and known bypass techniques. Use when assessing target hardening or planning exploit mitigation bypasses.
offensive-exploit-development
Exploit development operational guide: environment setup, debugging workflow, PoC development lifecycle, writing reliable exploits, using pwntools/pwndbg, heap exploitation techniques, and weaponization considerations. Use when actively developing exploits or setting up an exploit dev environment.
offensive-tls-attacks
Comprehensive methodology for auditing and exploiting TLS/SSL implementations and misconfigurations across network services and mobile applications. Covers protocol downgrade attacks including POODLE (CVE-2014-3566) against SSLv3 CBC padding, DROWN (CVE-2016-0800) cross-protocol attack leveraging SSLv2 export ciphers…
offensive-advanced-redteam
Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…