agentmods.dev

asc-review-triage

asc-review-triage is a skill for Claude Code, Codex from pofky/asc-mcp. It costs 102 tokens per session (789 once invoked), scanned A, original, MIT.

A workflow for collecting and sorting reviews of an iPhone or Mac app from the App Store, including ratings and recurring themes.

In plain words
What is it for?
Finding low-rated reviews, summarizing user complaints, checking rating patterns, and relating changes to an app version under review.
Why use it?
It turns scattered customer feedback into a focused view of common problems and sentiment.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

not rated 0repo 5d ago A scan 102 tokens original MIT

Good fit Finding low-rated reviews, summarizing user complaints, checking rating patterns, and relating changes to an app version under review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pofky/asc-mcp/asc-review-triage
View source ↗ pofky/asc-mcp pofky.github.io
Install

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.

Any agent
npx skills add pofky/asc-mcp --skill asc-review-triage
Clone the repo
git clone --depth 1 https://github.com/pofky/asc-mcp

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for asc-review-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/pofky/asc-mcp/asc-review-triage/github.svg)](https://agentmods.dev/skills/pofky/asc-mcp/asc-review-triage)
Your own site
<a href="https://agentmods.dev/skills/pofky/asc-mcp/asc-review-triage"><img src="https://agentmods.dev/badge/skills/pofky/asc-mcp/asc-review-triage/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.

agentmods 80×15 button for asc-review-triage

Your own site · 80×15
<a href="https://agentmods.dev/skills/pofky/asc-mcp/asc-review-triage"><img src="https://agentmods.dev/badge/skills/pofky/asc-mcp/asc-review-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 789 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00102 $0.00789
Opus 5 $0.00051 $0.00394
Sonnet 5 $0.00020 $0.00158
Haiku 4.5 $0.00010 $0.00079

Measured 12d ago against content hash d60cf3d84212, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

asc-review-triage 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.

skills/asc-review-triage/SKILL.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

App Store review triage

When the user asks about reviews, ratings, or customer feedback for their App Store apps, follow this procedure using the asc-mcp tools.

Step 1. Identify the app

If the user specified an app name or ID, use it. Otherwise:

  1. Call list_apps to get the full list.
  2. If there is only one app, use it.
  3. If there are several, ask the user which app they mean. Do not guess.

Step 2. Pull reviews

Call list_reviews with:

  • app_id: the app ID from step 1
  • rating: 3 (covers 1, 2, and 3 star reviews when sorted correctly)
  • sort: newest
  • limit: 20 for a quick scan, up to 100 for a deep dive

If the user specifically asked about 1-star reviews only, set rating: 1. If they asked about all reviews (positive and negative), call list_reviews without a rating filter.

Step 3. Confirm review status

Call review_status with the same app_id. This tells the user whether a new version is in review or waiting, which often correlates with review-score dips.

Step 4. Summarize

Produce a concise summary with:

  • Total reviews in the window
  • Breakdown by rating (1, 2, 3, 4, 5)
  • 3 to 5 themes, each with a review-count and one representative quote
  • Any single review flagged as potentially actionable (specific bug report, feature request, competitor mention)
  • The current review-queue status from step 3

Guardrails

  • Do not invent reviews. Quote only what list_reviews returned.
  • Do not post a reply. This skill reads only. Drafting or posting responses is a separate Pro feature not in this skill.
  • If list_reviews returns nothing, say so plainly.
  • On the free tier, list_reviews refuses instead of returning reviews. Say so plainly, then offer the trial: asc_start_trial unlocks every tool for 7 days with no card and takes effect in the running session. It needs the user's real email, so ask for it rather than inventing one, and do not call it unprompted. If they would rather just subscribe, Pro is $9 a month at https://buy.polar.sh/polar_cl_y86PS4ruc848PXevVvSYS49S8gZY8JYWF192v1UEgjj.

Read the full file on GitHub · 59 lines

Changes

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.

  1. 12d ago First seen · 59 lines · 102 tokens per session scan A d60cf3d84212

Subscribe to this mod's changes

asc-review-triage is a skill published in the GitHub repository pofky/asc-mcp (0 stars, last pushed 5d ago), licensed MIT. It adds 102 tokens to every session and 789 once invoked, about $0.0005 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-31.

Analytics and metricsClaude CodeResearchai-agentapp-store-connectapplecursordeveloper-tools
Related

Other skills, from other repositories

apple-cleanup

Exhaustive engineering hardening of an iOS app. Reviews for Swift 6 compliance, crash risks, App Store rejection risks, and tech debt; builds a surgical plan; dispatches parallel subagents to fix all P0-P2 issues; then pushes an alpha to TestFlight. Use for pre-submission cleanup and code hardening, not design polish.

markdavidgan/apple-dev-skills · 77 tokens

ios-test

XCTest patterns for unit tests, UI tests, and SwiftData testing with in-memory containers under Swift 6 strict concurrency, plus test performance budgets. Use when writing or fixing tests, setting up test targets, testing SwiftData models, or planning CI test suites. Trigger on "write a test", "unit test", "XCTest"…

markdavidgan/apple-dev-skills · 100 tokens

apple-polish

Design and keynote-readiness craftsmanship review of an iOS app. Evaluates through Jony Ive (visual obsession) and Steve Jobs (demo readiness) perspectives, presents prioritized findings, then orchestrates parallel agents to fix selected issues and push a TestFlight build. Use for design polish, not engineering bugs.

markdavidgan/apple-dev-skills · 65 tokens

apple-review

Comprehensive Apple-grade review of an iOS app covering design (Apple design leader perspective), engineering (architecture and code quality), compliance (App Store rejection risks), and keynote readiness (product story and demo quality). Use when asked for a full app review, Apple-quality audit, design critique, HIG…

markdavidgan/apple-dev-skills · 88 tokens

swift6-concurrency

Handle Swift 6 concurrency patterns. Use when encountering Sendable warnings, data race errors, MainActor isolation issues, or framework interop problems (EventKit, Speech, AVFoundation, etc.). Trigger on "Swift 6 error", "Sendable", "data race", "MainActor", "concurrency warning", or "strict concurrency".

markdavidgan/apple-dev-skills · 74 tokens

app-rejection-recovery

Diagnoses App Store rejections, drafts Resolution Center responses, and plans the fix for resubmission. Use when the user says "my app was rejected", "Apple rejected my app", "App Review rejection", "guideline violation", "Resolution Center response", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "binary…

markdavidgan/apple-dev-skills · 132 tokens