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 sachin0034-tech/mini-pm --skill user-researchgit clone --depth 1 https://github.com/sachin0034-tech/mini-pmWrote 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/sachin0034-tech/mini-pm/user-research)<a href="https://agentmods.dev/skills/sachin0034-tech/mini-pm/user-research"><img src="https://agentmods.dev/badge/skills/sachin0034-tech/mini-pm/user-research.svg" alt="Measured on agentmods" 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.00083 | $0.00660 |
| Opus 5 | $0.00042 | $0.00330 |
| Sonnet 5 | $0.00017 | $0.00132 |
| Haiku 4.5 | $0.00008 | $0.00066 |
Grade A, and why
user-research 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 7d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Research Synthesizer
Trigger
Activate on "synthesize research", "analyze interviews", "research findings", "interview synthesis".
Behavior
Step 1: Get Input
Ask:
- Paste the research notes or interview transcripts
- What was the research question?
- How many participants?
Step 2: Synthesize
Key Findings (ranked by evidence strength) For each:
- Finding (1 sentence)
- Evidence (how many participants, quotes)
- Confidence (High/Medium/Low)
- Product implication
Themes | Theme | Frequency | Representative Quote | Implication |
Surprises
- What contradicted our assumptions
Gaps
- Questions not answered, segments not covered
Recommended Actions
- Prioritized list with supporting evidence
Example
Bad synthesis (no evidence, no confidence levels):
Key Findings:
- Users like the product
- Onboarding could be better
- Some people want more features
Good synthesis:
Key Findings (ranked by evidence strength):
1. Users abandon onboarding at the "connect integrations" step
Evidence: 7 of 10 participants hesitated or failed here. 4 said
variants of "I don't want to give access to my data yet."
Confidence: HIGH
Implication: Move integrations to post-activation. Let users see
value before asking for trust.
2. Power users create personal workarounds for batch editing
Evidence: 3 of 10 participants (all daily users) showed custom
keyboard shortcuts or browser extensions they built themselves.
Confidence: MEDIUM (small sample of power users)
Implication: Batch editing is a retention lever for heaviest users.
Worth exploring, but validate with usage data first.
Surprises:
- 6 of 10 participants didn't know the search feature existed. It's
behind a keyboard shortcut (Cmd+K) with no visible UI entry point.
This contradicts our assumption that search is well-adopted.
Gaps:
- No participants from enterprise segment (>500 employees). Findings
may not generalize to that tier.
- Research question about pricing sensitivity was not explored — all
participants were on free plans.
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.
- 7d ago First seen · 87 lines · 0 tokens per session scan A 3c0b5c309d88
user-research is a skill published in the GitHub repository sachin0034-tech/mini-pm (4 stars, last pushed 4mo ago), licensed MIT. It adds 83 tokens to every session and 660 once invoked, about $0.0004 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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…