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 skills add cenconq25/claude-code-app-studio --skill prd-reviewgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/prd-review)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/prd-review"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/prd-review/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/skills/cenconq25/claude-code-app-studio/prd-review"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/prd-review.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.00086 | $0.02302 |
| Opus 5 | $0.00043 | $0.01151 |
| Sonnet 5 | $0.00017 | $0.00460 |
| Haiku 4.5 | $0.00009 | $0.00230 |
Grade A, and why
prd-review 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 5d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review a PRD
Independent review gate for a single PRD. The reviewer must be in a fresh session so it does not inherit the authoring context — a PRD that "felt right while writing" can still fail review.
Output: a printed verdict + structured blockers list. Optionally writes a .review.md sibling file.
Purpose / When to Run
Run when:
- A PRD has just been finished by
/design-system - A PRD has been retrofit from extracted code
- A reviewer wants a second pass on a previously-approved PRD that has changed
Do not run when:
- The PRD is incomplete (sections still
[To be designed]) → run/design-systemfirst - The PRD has not yet been written → run
/design-systemfirst
Inputs
- Path to a PRD file (required)
design/concept.mdfor pillar checks- Dependency PRDs from
design/systems-index.md design/registry/entities.yaml
Outputs
- A verdict:
APPROVED,NEEDS REVISION, orMAJOR REVISION - A structured blockers list
- Optional:
<prd-path>.review.mdsnapshot written
Phase 1: Resolve Path and Confirm Doc Type
If the argument is a system name (not a path), check design/prd/<name>.md. If exists, use it. If multiple matches, ask which.
If no argument, glob design/prd/*.md and ask:
- Prompt: "Which PRD should I review?"
- Options: list of files (use AskUserQuestion if ≤ ~6, else free text)
If the file does not exist, stop with a clear error.
Doc-type guard: this skill is for PRDs only. If the resolved file is
not a PRD (no ## Detailed Requirements with TR- IDs and not under
design/prd/), stop and recommend /design-review <path> instead. Do
not run PRD checks against a non-PRD doc.
Phase 2: Read Context
Read:
- The target PRD in full
design/concept.mdfor principle and metric alignmentdesign/systems-index.mdto identify dependencies- For each listed dependency, read the dependency PRD's interface sections
design/registry/entities.yaml.claude/docs/technical-preferences.md(framework + min OS)
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.
- 5d ago First seen · 250 lines · 86 tokens per session scan A 046451a5d492
prd-review is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 86 tokens to every session and 2,302 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
orca-emulator-android
Android device and emulator control from inside Orca over adb, with the live device view in Orca's emulator pane. Use when driving an adb-connected emulator or phone on Windows, Linux, or macOS: booting AVDs, taps, swipes, typing, hardware buttons, rotation, app install and launch, runtime permissions, the…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.