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 kelegele/oh-my-pm --skill feedback-synthesisgit clone --depth 1 https://github.com/kelegele/oh-my-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/kelegele/oh-my-pm/feedback-synthesis)<a href="https://agentmods.dev/skills/kelegele/oh-my-pm/feedback-synthesis"><img src="https://agentmods.dev/badge/skills/kelegele/oh-my-pm/feedback-synthesis/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/kelegele/oh-my-pm/feedback-synthesis"><img src="https://agentmods.dev/badge/skills/kelegele/oh-my-pm/feedback-synthesis.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.00095 | $0.02794 |
| Opus 5 | $0.00048 | $0.01397 |
| Sonnet 5 | $0.00019 | $0.00559 |
| Haiku 4.5 | $0.00010 | $0.00279 |
Grade A, and why
feedback-synthesis 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.
How it starts
The opening of the file, as written. The whole thing — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feedback Synthesis
Turn user noise into actionable insights.
What This Skill Does
Aggregates feedback from multiple sources, identifies themes and patterns, categorizes by severity and frequency, and synthesizes into actionable insights. Makes sense of scattered user input.
When to Use
Activate this skill when:
- User needs to analyze feedback from any source
- Phrases like "analyze feedback", "what are users saying", "synthesize feedback"
- Reviewing feedback for planning or prioritization
- Understanding user sentiment and themes
- User says "what do users think" or "feedback analysis"
How It Works
The synthesis process ensures comprehensive feedback understanding:
- Collect feedback - Gather from all sources
- Deduplicate - Remove duplicates and merge related
- Categorize - Group by theme, type, severity
- Quantify - Count frequency, measure sentiment
- Prioritize - Rank by impact and urgency
- Synthesize - Generate insights and recommendations
Input Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
sources |
list | No | Feedback sources (default: all available) |
timeframe |
string | No | Period to analyze (default: "last 30 days") |
focus |
string | No | Specific feature or area to focus on |
Feedback Sources
| Source | Type | What It Provides |
|---|---|---|
| Support tickets | Structured | Detailed issues, urgent problems |
| App reviews | Public | Overall sentiment, common complaints |
| User interviews | Qualitative | Deep insights, nuanced feedback |
| Surveys | Structured | Quantifiable satisfaction, NPS |
| In-app feedback | Contextual | Real-time, situation-specific |
| Social media | Public | Brand perception, common requests |
| Sales/CS notes | Filtered | Prospect/customer requests |
Output Structure
The skill generates synthesis outputs:
- Feedback summary - High-level overview of themes
- Categorized items - Feedback grouped by type
- Prioritized list - Ranked for action
- Sentiment analysis - Overall user sentiment trends
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 · 295 lines · 95 tokens per session scan A 766a5c60c6f0
feedback-synthesis is a skill published in the GitHub repository kelegele/oh-my-pm (4 stars, last pushed 1mo ago), licensed MIT. It adds 95 tokens to every session and 2,794 once invoked, about $0.0005 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
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.