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 review-all-prdsgit 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/review-all-prds)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/review-all-prds"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/review-all-prds/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/review-all-prds"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/review-all-prds.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.00058 | $0.02235 |
| Opus 5 | $0.00029 | $0.01118 |
| Sonnet 5 | $0.00012 | $0.00447 |
| Haiku 4.5 | $0.00006 | $0.00224 |
Grade A, and why
review-all-prds 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 6d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review All PRDs (Holistic)
Single-PRD review catches missing sections. This skill catches interaction failures between PRDs that look fine alone but collide once shipped together: the paywall blocks the empty-state CTA, two systems both want primary tab position, the onboarding promises a feature gated by a paywall the user has not seen, the analytics event vocabulary is inconsistent across systems.
Read-only. Produces a printed report. The user runs /propagate-design-change or /design-system retrofit ... to resolve findings.
Purpose / When to Run
Run when:
- All v1 PRDs are individually
APPROVED - Before
/create-architecture— architecture should not codify contradictions - Before any major launch milestone
- After a batch of PRD changes (3+ PRDs touched in a sprint)
Distinct from /consistency-check (value drift) — this skill assesses design intent, flow continuity, and system overlap.
Inputs
- All
design/prd/*.md design/concept.mddesign/systems-index.mddesign/registry/entities.yamldesign/design-bible.mdif present
Outputs
- A printed structured report. No file writes.
Phase 1: Pre-Check
Verify all MVP-scoped PRDs are individually APPROVED. Read design/systems-index.md and confirm Status column.
If any PRD is not yet APPROVED, ask:
- Prompt: " PRDs are not yet APPROVED. Run holistic review anyway, or stop and fix individual PRDs first?"
- Options:
Run anyway (degraded),Stop,Show me which PRDs aren't approved
If user proceeds with degraded run, mark the report header accordingly.
Phase 2: Read Everything
Read all PRDs. Hold them in context simultaneously — that is the point of the skill (and why it runs on the opus tier).
Build cross-PRD summaries:
- Screen-by-screen map — for each screen referenced across PRDs, list every PRD that touches it
- Event vocabulary — every analytics event mentioned, by name, sorted; flag near-duplicates (
paywall_shown,paywallShown,payway_shown) - Configurable values — every value name across PRDs
- Cross-system flows — every flow that crosses 2+ systems (e.g., "user signs up → first session → first paywall trigger")
- Permission asks — every iOS/Android permission requested across PRDs (notifications, camera, location, contacts, photos)
- Background work — every system that schedules background tasks
- Push notifications — every category / channel / trigger across PRDs
- Tabs / nav slots — every system that wants top-level tab placement
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.
- 6d ago First seen · 244 lines · 58 tokens per session scan A f28a09061ff6
review-all-prds is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 2,235 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.