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 drivestream-lab/prayog-skills --skill review-product-questionsgit clone --depth 1 https://github.com/drivestream-lab/prayog-skillsWrote 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/drivestream-lab/prayog-skills/review-product-questions)<a href="https://agentmods.dev/skills/drivestream-lab/prayog-skills/review-product-questions"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/review-product-questions/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/drivestream-lab/prayog-skills/review-product-questions"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/review-product-questions.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.00098 | $0.00955 |
| Opus 5 | $0.00049 | $0.00477 |
| Sonnet 5 | $0.00020 | $0.00191 |
| Haiku 4.5 | $0.00010 | $0.00096 |
Grade A, and why
review-product-questions 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review product questions (PE stance — optional)
Interactive pass for a PE with product perspective: refine codebase-grounded
questions and PE recommendations before /post-product-questions.
Optional. Some PEs skip this and post the map as-is.
Not PM authority. Refined stances are still proposals for PM on the Meta PR.
Not /validate-requirements / /update-documents / PRD edits.
Question shape: ../references/product-question-template.md.
Handoff: ../references/handoff-adjunct.md.
When to use
| Use | Skip |
|---|---|
| PE wants to sharpen scenarios / pick a recommended stance | PE only wants to publish map questions |
| Senior PE owning product tradeoffs with eng evidence | Hand all product calls to PM untouched |
NON-NEGOTIABLE
- Read one map (or prior stance file) — do not re-run graphs.
- Present each question with scenario, example, recommendation, why, alternatives, evidence before asking how to refine.
- Prefer AskQuestion when available; otherwise chat options and wait.
- Record refined PE stance into
out/reports/PE-Product-Stance-{INIT}.md(or pe-workspace equivalent). - Label every decision as
pe_proposal— neverpm_approved. - Do not edit the PRD or outline.
gate_coupled: false. Noimpact-map-*/spec-*mutations.- After this skill, typical next step is
/post-product-questions(uses stance file when present).
Inputs
- Map path — (REQUIRED)
PRD-Codebase-Map-{INIT}.md - Mode — all / conflicts-only / PE-selected IDs
Process
Phase 1 — Setup
- Parse § Product questions (
PQ-*). - Summarize counts by delta.
- Entry gate AskQuestion:
- refine-all — Walk all questions interactively
- conflicts-only — Walk conflict/partial only
- skip — Skip; go to /post-product-questions with raw map
Phase 2 — Per question (PE refine)
For each selected question, show full template fields, then:
What ships with it
1 file 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 Changed 83fb9b4f6aab
- 12d ago First seen · 111 lines · 98 tokens per session scan A 3c821667a9dc
review-product-questions is a skill published in the GitHub repository drivestream-lab/prayog-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 98 tokens to every session and 955 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…