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 daehounan/agency-agents-fork --skill product-discovery-routinggit clone --depth 1 https://github.com/daehounan/agency-agents-forkWrote 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/daehounan/agency-agents-fork/product-discovery-routing)<a href="https://agentmods.dev/skills/daehounan/agency-agents-fork/product-discovery-routing"><img src="https://agentmods.dev/badge/skills/daehounan/agency-agents-fork/product-discovery-routing/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/daehounan/agency-agents-fork/product-discovery-routing"><img src="https://agentmods.dev/badge/skills/daehounan/agency-agents-fork/product-discovery-routing.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.00115 | $0.00387 |
| Opus 5 | $0.00057 | $0.00193 |
| Sonnet 5 | $0.00023 | $0.00077 |
| Haiku 4.5 | $0.00012 | $0.00039 |
Grade A, and why
product-discovery-routing 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 11d 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.
What it actually says
Product Discovery Routing Skill (Niche)
Scope intentionally narrow. For most product work use existing skills:
- Sprint planning →
product-management:sprint-planning - PRD / spec →
product-management:write-spec - Roadmap →
product-management:roadmap-update - Stakeholder update →
product-management:stakeholder-update - Research synthesis →
product-management:synthesize-research - Competitive brief →
product-management:competitive-brief - Brainstorming →
product-management:brainstorm/product-management:product-brainstorming - Metrics review →
product-management:metrics-review - Feedback synthesis →
product-management:synthesize-research - Interactive PRD →
ecc:prp-prd
When to use THIS skill
Only when the work is one of these two niches:
| User signal | Agent to invoke |
|---|---|
| Behavioral psychology, habit loops, nudge architecture, engagement design, motivational systems | product-behavioral-nudge-engine |
| Narrative-rich market trend analysis with persona depth (not structured competitive brief) | product-trend-researcher |
When NOT to use
Anything covered by product-management:* — use those directly. They are stronger and more current.
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.
- 11d ago First seen · 32 lines · 115 tokens per session scan A 371050df4fcc
product-discovery-routing is a skill published in the GitHub repository daehounan/agency-agents-fork (2 stars, last pushed 3mo ago), licensed MIT. It adds 115 tokens to every session and 387 once invoked, about $0.0006 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
cognito
AWS Cognito user authentication and authorization service. Use when setting up user pools, configuring identity pools, implementing OAuth flows, managing user attributes, or integrating with social identity providers.
sns
AWS SNS notification service for pub/sub messaging. Use when creating topics, managing subscriptions, configuring message filtering, sending notifications, or setting up mobile push.
iam
AWS Identity and Access Management for users, roles, policies, and permissions. Use when creating IAM policies, configuring cross-account access, setting up service roles, troubleshooting permission errors, or managing access control.
i18n-parity
MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored READMEs, locale-aware formatting, language switchers) in parity across every supported language. Use automatically (without being asked) whenever you add or change…
dag-map
Render the multi-agent orchestration DAG for a session — parent→child subagent edges, tree depth, and fan-out — from the Agent Monitor workflow intelligence API. Cross-checks the orchestration dataset against the raw agent records and session detail. Use when visualizing how a session's agent structure was organized.
update-project-docs
MANDATORY for every coding agent (Claude Code, Codex, or any other) — keep this repository's documentation in sync after any change to behavior, configuration, interfaces, events, schema, or features. Use automatically (without being asked) at the end of ANY change-set that adds or alters an env var, event type, hook…