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 stanislavnianko/product-discovery-claude-skills --skill profile-buildergit clone --depth 1 https://github.com/stanislavnianko/product-discovery-claude-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/stanislavnianko/product-discovery-claude-skills/profile-builder)<a href="https://agentmods.dev/skills/stanislavnianko/product-discovery-claude-skills/profile-builder"><img src="https://agentmods.dev/badge/skills/stanislavnianko/product-discovery-claude-skills/profile-builder/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/stanislavnianko/product-discovery-claude-skills/profile-builder"><img src="https://agentmods.dev/badge/skills/stanislavnianko/product-discovery-claude-skills/profile-builder.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.00114 | $0.01627 |
| Opus 5 | $0.00057 | $0.00813 |
| Sonnet 5 | $0.00023 | $0.00325 |
| Haiku 4.5 | $0.00011 | $0.00163 |
Grade A, and why
profile-builder 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 12d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Profile Builder
Foundation skill of the discovery-phase skill pack ·
foundationgroup · writesdiscovery-context.md, the file every other skill in the pack reads.
Produces discovery-context.md — the single source of truth that every other skill in this pack reads. Without it, other skills will warn and offer to bootstrap inline (a 2–3 question mini-interview held in conversation, not written to disk). Running this skill first gives the best, most consistent results.
Activation rule
The moment this skill triggers, go straight to the interview. Do not summarise the skill, do not ask permission, do not explain the structure. The user already knows what they activated.
What this skill writes
A single file at the project root: discovery-context.md.
It contains 7 sections:
- Client
- Product / Initiative
- Engagement
- Access & Data
- Expected deliverable
- Constraints
- Open questions about the engagement itself
See ./template.md for the exact structure.
Procedure
Step 1 — Check for existing context
If discovery-context.md already exists in the project root:
- Show the user a 5-line summary of what's there.
- Ask: "Do you want to refresh (re-interview from scratch), update (only the section I name), or keep (just confirm and exit)?"
- Route accordingly. Default to "update" if unclear.
If the file doesn't exist, proceed to Step 2.
Step 2 — Interview, in 4 batches
Use AskUserQuestion. Group questions to minimize round-trips.
Batch A — Client
- Client name and short description (1 sentence)
- Domain / industry
- Business model: B2B SaaS / B2C product / marketplace / services / internal tool / other
- Stage: pre-launch / early traction / scaling / mature / declining
- Decision-makers: who signs off on what (names/roles)
- Existing relationship: new logo / repeat client / staff aug / pre-sale prospect
Batch B — Product / Initiative
- What's being explored (one sentence)
- Current state of the thing: idea / spec / prototype / live but failing / live but pivoting
- Prior research / artifacts available (links, file names, or "none")
- Has the client already proposed a solution or feature list? (yes / no — and if yes, summarize it)
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.
- 12d ago First seen · 139 lines · 114 tokens per session scan A 7a2c44cda33b
profile-builder is a skill published in the GitHub repository stanislavnianko/product-discovery-claude-skills (1 stars, last pushed 4mo ago), licensed MIT. It adds 114 tokens to every session and 1,627 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
jtbd-extractor
Turn raw research into Jobs-to-be-Done statements showing what users are really trying to accomplish. Use when: extract jobs, jtbd analysis, jobs to be done, what job is the user hiring, underlying user needs.
assumption-mapper
Surfaces the assumptions a product or strategy depends on, classifies them by criticality and evidence quality, and produces a prioritized test plan. Use when: assumption mapping, identify assumptions, what could go wrong, leap-of-faith assumptions, riskiest assumption test, RAT, assumption inventory, validate before…
competitive-analyzer
Structured competitive teardown for product discovery - surface the 4-6 dimensions buyers actually weigh, score every competitor on each, and identify exploitable gaps. Use when: competitive analysis, competitor teardown, market positioning, where do we win, where do we lose, competitive gap analysis, competitor audit.
feedback-prioritizer
Triages a backlog of raw customer feedback into a ranked list of opportunities scored on reach, severity, strategic fit, and confidence. Outputs a prioritized list with explicit "do not act" callouts for vocal-minority signals. Use when: triage feedback, prioritize feature requests, customer feedback backlog, what…
north-star-metric-finder
Identifies a candidate North Star Metric (NSM) for a product - the single metric that captures the value the product delivers to its customers and predicts long-term business growth. Tests candidates against five criteria and surfaces input metrics that move it. Use when: north star metric, NSM, single metric that…
prd-taskmaster
Zero-config goal-to-tasks engine (the Atlas engine). Takes any goal (software, pentest, business, learning), runs adaptive discovery via brainstorming, generates a validated spec, parses into TaskMaster tasks, and hands off to execution. Use when user says "PRD", "product requirements", "I want to build", invokes…