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 daffy0208/ai-dev-standards --skill customer-feedback-analyzergit clone --depth 1 https://github.com/daffy0208/ai-dev-standardsWrote 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/daffy0208/ai-dev-standards/customer-feedback-analyzer)<a href="https://agentmods.dev/skills/daffy0208/ai-dev-standards/customer-feedback-analyzer"><img src="https://agentmods.dev/badge/skills/daffy0208/ai-dev-standards/customer-feedback-analyzer/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/daffy0208/ai-dev-standards/customer-feedback-analyzer"><img src="https://agentmods.dev/badge/skills/daffy0208/ai-dev-standards/customer-feedback-analyzer.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.00057 | $0.02518 |
| Opus 5 | $0.00028 | $0.01259 |
| Sonnet 5 | $0.00011 | $0.00504 |
| Haiku 4.5 | $0.00006 | $0.00252 |
Grade A, and why
customer-feedback-analyzer 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 9d 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.
This is a copy
100% identical to customer-feedback-analyzer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 470 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Feedback Analyzer
Collect, analyze, and prioritize user feedback to inform product decisions.
Core Principle
Never collect feedback you won't act on. Collecting feedback creates expectation of action. If you can't commit to reviewing and acting on it, don't ask for it. Destroys trust.
Feedback Channels
1. In-App Feedback Widget
Best for: Contextual feedback, low friction
// Contextual feedback
<FeedbackWidget
context={{
page: 'dashboard',
feature: 'export',
user_action: 'clicked_export'
}}
placeholder="How can we improve exports?"
/>
Pros: High quality (contextual), immediate Cons: Can interrupt user flow
2. NPS Surveys
Best for: Measuring overall satisfaction and loyalty
Question: "How likely are you to recommend [Product] to a friend or colleague?"
Scale: 0-10
Scoring:
Promoters (9-10): Love your product, will advocate
Passives (7-8): Satisfied but not enthusiastic
Detractors (0-6): Unhappy, will churn
NPS = % Promoters - % Detractors
Benchmarks:
Excellent: ≥50
Good: 30-49
Needs Work: <30
Follow-up question: "What's the main reason for your score?"
3. Support Tickets
Best for: Identifying recurring issues
Pattern Recognition:
- Same issue reported 5+ times → UX problem, not edge case
- Support time > 10 min per ticket → Needs better docs
- Ticket volume spike → Recent deploy likely caused issue
4. User Interviews
Best for: Deep qualitative insights
Interview Structure:
1. Background (5 min): Their role, use case
2. Problem Discovery (10 min): Challenges they face
3. Solution Validation (10 min): Show prototype, get reaction
4. Wrap-up (5 min): Any other feedback?
Sample Size: 5-10 users per persona
5. Feature Request Voting
Best for: Prioritizing roadmap
Tools: Canny, ProductBoard, Upvoty
Benefits:
- See most requested features
- Reduce duplicate requests
- Public roadmap transparency
- Close the loop automatically
Avoid:
- Building everything requested
- Letting voters drive strategy
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.
- 9d ago First seen · 470 lines · 57 tokens per session scan A 9dd454c3b8dc
customer-feedback-analyzer is a skill published in the GitHub repository daffy0208/ai-dev-standards (36 stars, last pushed 8mo ago), licensed MIT. It adds 57 tokens to every session and 2,518 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to customer-feedback-analyzer, differing in 0 lines, and is treated as a copy.
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-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…