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 HoangNguyen0403/agent-skills-standard --skill review-product-valuegit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/review-product-value)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/review-product-value"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/review-product-value/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/hoangnguyen0403/agent-skills-standard/review-product-value"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/review-product-value.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.00023 | $0.01414 |
| Opus 5.5 | $0.00009 | $0.00566 |
| Sonnet 5.5 | $0.00005 | $0.00283 |
| Haiku 4.5 | $0.00002 | $0.00141 |
Grade A, and why
review-product-value 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 3d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Product Value Skill
[!IMPORTANT] Review realized product value against registered measurement contracts and baseline evidence, separating delivery completion from causal ROI.
Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.
Instructions
When the user asks to perform this workflow, execute the following steps:
Review Product Value Workflow
Goal: Evaluate post-release product value by comparing observed outcomes against registered metrics and investment assumptions without inferring causal ROI from delivery alone.
Steps
- Preflight and intake:
- Preflight: verify
product-management/product-evidence,product-management/product-metrics,product-management/product-investment; conditionalproduct-management/product-roadmaponly if proposing ordering changes. Scripts:scripts/validate-product-evidence.mjs(ordinary<root>/product-management/product-evidence, Kiro<root>/product-management-product-evidence),scripts/evaluate-investment.mjs(ordinary<root>/product-management/product-investment, Kiro<root>/product-management-product-investment). Validator invocation:node <validator> <ledger.json> --authority-root <canonical-root> --as-of <UTC> --gate release(orstructural). Calculator invocation:node <calculator> <scenario.json>. Exit:0= coherent (structural, readiness not_assessed) or gate eligible for host check only; never authorization;3= proposal_only/gap;1/2/4= error (never validated). Emit exact gap strings (<pkg> not installed; opt in at a reviewed ref and sync,product-management/product-evidence excluded; opt in at a reviewed ref and sync,validate-product-evidence.mjs missing; repair package,evaluate-investment.mjs missing; repair package,Node >=20 unavailable; calculation not performed,analytics evidence unavailable; value inconclusive) with safe next action; preserve deliveryfeature_status. Seeproduct-evidenceVerification Workflow. - Intake:
slug, scope, original investment ref (historical attribution only, not action authority), registeredMETcontracts, and comparison window. No automated background scheduler.
- Preflight: verify
- Inspect measurement contracts and evidence:
- Audit MET contracts (AC-009): verify
status(planned|instrumented|observed|unavailable; noimmaturestatus enum), exactquery_revision= query origin revision,eligibility/cohort, baseline XOR scopedbaseline_exception(purpose: "release",outcome: "risk_accept"),measurement_owner, andreview_trigger. On failure, record precisemissing_evidencegap and returninconclusive, never invented observations. - Retrieve observed
SRCdata and actual incremental costs. Check displaced work / opportunity cost rationale. Retain paired financial input/result (financial_input,financial_result/ horizon) separately.
- Audit MET contracts (AC-009): verify
- Assess attribution and guardrails:
- Inspect guardrails (churn, errors, latency). If guardrail harm or regression is detected, escalate immediately to authorized incident controls (
incident-hotfix); agents cannot autonomously roll out or revert. - Evaluate causal attribution: classify as
causal_supported | descriptive | unknown. Document confounders (marketing, seasonality, pricing) and counterfactuals.scaleandcausal_supportedrequire observed metrics plus sources. Never infer causal ROI from release.
- Inspect guardrails (churn, errors, latency). If guardrail harm or regression is detected, escalate immediately to authorized incident controls (
- Formulate advisory recommendation:
- Emit
REVrecord with recommendation:scale | iterate | stop | inconclusive. Record explicit limitations.REV.decisionis historical attribution only; any capital, roadmap, or retirement action requires a separate recordedvalue_review/ host decision. - Recommendations are advisory; emit host decision needed for any capital, roadmap, or retirement action.
- Preserved delivery invariant: keep delivery
feature_status(e.g.releasedorverified) unchanged even when product value is inconclusive; never setblockedfor product-evidence gaps alone.
- Emit
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.
- 3d ago First seen · 76 lines · 23 tokens per session scan A 3d0b3cbe4bdb
review-product-value is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (578 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 1,414 once invoked, about $0.0001 per session on Opus 5.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-10-16.
Other skills, from other repositories
intelligence-docs
Keeps the CopilotKit Intelligence landing page in sync when a new Intelligence feature ships or when Intelligence docs are added, renamed, or removed. Use when adding Intelligence capabilities, writing or moving pages under docs/intelligence, editing IntelligenceFeatureCards, or changing…
nextjs-idioms
Next.js App Router architecture: React Server Components (RSC), Server Actions, nested layouts, route handlers, and streaming. Use when building or refactoring Next.js web applications. Pair with react-idioms and typescript-idioms.
react-idioms
React 19+ patterns: custom hooks, Suspense boundaries, state management, component composition, and web performance. Use when developing or refactoring React components and client applications. Pair with typescript-idioms.
plan
PM planning workflow that gathers requirements, decomposes them into prioritized tasks, defines API contracts, and produces both a machine-readable plan and a human-readable tracker in docs/plans/.
coordinate-pro
Thorough version of coordinate - high-quality development workflow with 11 review steps out of 17.
coordinate
Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.