PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.
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.
git clone --depth 1 https://github.com/mohitagw15856/pm-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/rules/mohitagw15856/pm-claude-skills/multi-source-signal-synthesiser)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/multi-source-signal-synthesiser"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/multi-source-signal-synthesiser/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/rules/mohitagw15856/pm-claude-skills/multi-source-signal-synthesiser"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/multi-source-signal-synthesiser.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.00089 | $0.00862 |
| Opus 5 | $0.00044 | $0.00431 |
| Sonnet 5 | $0.00018 | $0.00172 |
| Haiku 4.5 | $0.00009 | $0.00086 |
Grade A, and why
multi-source-signal-synthesiser 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 8d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Source Signal Synthesiser Skill
Reconcile user signals from multiple sources — interviews, support tickets, NPS, app reviews, sales calls — into a unified, weighted insight brief that surfaces the underlying need rather than the surface-level request.
Required Inputs
Ask the user for these if not provided:
- Signal sources (interviews, support tickets, NPS verbatims, app reviews, sales calls, analytics — any combination)
- Time period covered by the data
- Product area or feature the signals relate to (if scoped)
Source Weighting (default — adapt to context)
| Source | Weight | Rationale |
|---|---|---|
| Direct research (interviews, usability tests) | 5 | Highest-fidelity, structured |
| Support tickets (unprompted pain signals) | 4 | Real pain, unfiltered |
| NPS verbatims | 3 | Broad but shallow |
| App store reviews | 2 | Public, self-selected |
| Sales call summaries | 2 | Filtered through sales lens |
| Anecdote or single report | 1 | Low confidence alone |
Process
- Tag each signal by source and apply weight
- Look for convergence: same underlying need appearing across 3+ sources
- Look for divergence: contradictory signals suggesting user segmentation
- Distinguish surface request from underlying need (e.g. "faster export" may mean "I don't trust the data will be there when I need it")
- Produce ranked insights by weighted frequency
- Validate — Confirm each insight has evidence from at least 2 source types. Flag any insight resting on a single source as low-confidence.
Output Structure
User Signal Synthesis — [Date / Period]
Sources included: [list with count per source] Total signals processed: [n]
Insight 1: [Underlying need, not feature request]
- Confidence: High / Medium / Low (based on source diversity and weight)
- Evidence: [Signals from each source supporting this]
- Conflicting signals: [Any contradicting evidence and how to interpret it]
- Product implication: [Specific next step, not generic]
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.
- 8d ago First seen · 72 lines · 89 tokens per session scan A 5ad55239aa34
multi-source-signal-synthesiser is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,357 stars, last pushed today), licensed MIT. It adds 89 tokens to every session and 862 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-09-03.
Other cursor rules, from other repositories
cursor
Always-on my-adhd-caveman. Off with "stop adhd-caveman" or "normal mode".
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.