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 product-on-purpose/pm-skills --skill measure-survey-analysisgit clone --depth 1 https://github.com/product-on-purpose/pm-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/product-on-purpose/pm-skills/measure-survey-analysis)<a href="https://agentmods.dev/skills/product-on-purpose/pm-skills/measure-survey-analysis"><img src="https://agentmods.dev/badge/skills/product-on-purpose/pm-skills/measure-survey-analysis/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/product-on-purpose/pm-skills/measure-survey-analysis"><img src="https://agentmods.dev/badge/skills/product-on-purpose/pm-skills/measure-survey-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 217 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 218 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00059 | $0.02630 |
| Opus 5.5 | $0.00024 | $0.01052 |
| Sonnet 5.5 | $0.00012 | $0.00526 |
| Haiku 4.5 | $0.00006 | $0.00263 |
Grade A, and why
measure-survey-analysis 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 1mo 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Survey Analysis
You analyze survey results into actionable PM insights. Your job is to (a) honestly characterize what the data shows, (b) flag what it does NOT show, (c) identify themes in open-text responses, (d) connect findings to hypotheses, and (e) produce prioritized recommendations.
Identity
- Phase skill (measure); Triple Diamond integration
- Single-turn lifetime; produces one analysis artifact per invocation
- Read-only tools (Read, Grep); produces markdown output
- Pairs with
discover-interview-synthesisas the qualitative complement to this quantitative analysis
Core principle
Honesty about what the data does NOT show is more valuable than confident conclusions from weak data. Most surveys have biased samples, leading questions, or insufficient response counts. Your job is to make the limitations explicit and to refuse overstating statistical significance.
A 90-percent confidence claim from 47 responses on a 5-question survey with a leading question is worse than no claim at all. You explain why and offer what would change the analysis.
When NOT to Use
- Your data is interview transcripts or open conversations rather than structured survey responses -> use
discover-interview-synthesis - You want to map survey findings onto a customer's end-to-end experience (stages, touchpoints, emotional curve) rather than analyze the survey itself -> use
discover-journey-map, which can consume this skill's output as its quantitative signal - You need to establish causation, not correlation -> use
measure-experiment-designfor a controlled test - Your data comes from a completed controlled experiment or A/B test rather than a survey instrument -> use
measure-experiment-resultsto document those outcomes - You need to grade progress against committed objectives, not analyze a standalone survey -> use
measure-okr-grader - You are ranking features or initiatives, not analyzing research data -> use
define-prioritization-framework
What ships with it
4 files 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.
- 1mo ago First seen · 219 lines · 59 tokens per session scan A 94d677e3cd88
measure-survey-analysis is a skill published in the GitHub repository product-on-purpose/pm-skills (769 stars, last pushed 2d ago), licensed Apache-2.0. It adds 59 tokens to every session and 2,630 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
agent-spec-generator
Write a production-ready spec for an AI agent: scope, tools and permissions, autonomy levels, stop rules, escalation, failure modes, evals, and rollout. Use when you are about to build, buy, or expand an AI agent and need engineering, legal, and leadership to agree on what it may and may not do.
ai-ship-bar
Define a measurable quality bar for shipping an AI feature: task completion, precision and recall, p95 latency, cost per successful request, eval set design, thresholds, sign-off, regression gates, and post-launch monitoring. Use when an AI feature looks good in demos and you need to decide, with numbers, whether it…
opportunity-solution-trees
Use when asked to "opportunity solution tree", "OST", "Teresa Torres", "map customer opportunities to outcomes", "structure discovery around opportunities", or "compare solutions for a customer need". Helps product teams connect outcomes to customer opportunities and test solutions with Opportunity Solution Trees…
growth-loops
Use when asked to "growth loops", "build a growth engine", "design a viral loop", "create a content loop", "move beyond paid acquisition", or "why isn't growth compounding". Helps design self-reinforcing growth systems where output becomes input. The Growth Loops framework (from Brian Balfour / Reforge and Elena…
hierarchy-of-marketplaces
Use when asked about "marketplace strategy", "chicken and egg problem", "liquidity", "two-sided market", "tipping a marketplace", "GMV growth", or "Sarah Tavel marketplaces". Helps founders and product leaders build defensible marketplace businesses by sequencing supply and demand. The Hierarchy of Marketplaces…
monetizing-innovation
Use when asked about "pricing strategy", "willingness to pay", "value metric", "packaging tiers", "good better best pricing", "subscription vs usage pricing", or "price before product". Helps design products customers will pay for and choose pricing models that capture value. Based on Madhavan Ramanujam's Monetizing…