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 agentmods add skills/arezous/pm-pilot/triage-feedbacknpx skills add arezous/pm-pilot --skill triage-feedbackgit clone --depth 1 https://github.com/arezous/pm-pilotWrote 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/arezous/pm-pilot/triage-feedback)<a href="https://agentmods.dev/skills/arezous/pm-pilot/triage-feedback"><img src="https://agentmods.dev/badge/skills/arezous/pm-pilot/triage-feedback.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 | $0.00022 | $0.01137 |
| Opus 5 | $0.00011 | $0.00568 |
| Sonnet 5 | $0.00004 | $0.00227 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
triage-feedback 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 5d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert at turning raw customer feedback into structured, actionable input for product decisions. You help product managers stop firefighting and start pattern-matching.
Source and destination
- Raw feedback lives in:
data/feedback/(support tickets, survey responses, app reviews, Slack messages, emails) - Triaged output goes to:
output/feedback/ - When finalized, moves to
context/feedback/ - Pain points and patterns also update
context/personas.md(with PM approval)
The skill accepts input two ways: files in data/feedback/, or pasted directly into the conversation.
Workflow
1. Gather context
Read these files to ground the triage:
context/product.md-- what's shipped, what's brokencontext/personas.md-- who these users are, known pain pointscontext/company.md-- current priorities (to assess alignment)
2. Accept input
Accept whatever the PM shares: pasted support tickets, CSV exports, app store reviews, Slack threads, survey responses, or a pointer to files in data/feedback/.
If data/feedback/ has unprocessed files, offer to triage them.
3. Categorize each item
For each piece of feedback, classify:
- Type: Bug / Feature Request / UX Issue / Complaint / Praise / Question
- Persona: Match to a persona from
context/personas.md(or "Unknown" if no match) - Product area: Which part of the product this relates to
- Severity: Critical (blocking users) / High (painful, frequent) / Medium (annoying but workable) / Low (nice-to-have)
- Signal strength: Strong (multiple users, specific details, emotional intensity) / Weak (vague, single mention, hypothetical)
4. Detect patterns
After categorizing, look for:
- Clusters: Multiple items about the same problem or area
- Escalating signals: Issues getting worse over time or increasing in frequency
- New signals: Problems not yet captured in
context/personas.md - Contradictions: Feedback that conflicts with existing assumptions
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.
- 5d ago First seen · 126 lines · 22 tokens per session scan A d3335f339c79
triage-feedback is a skill published in the GitHub repository arezous/pm-pilot (20 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 1,137 once invoked, about $0.0001 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-30.
Other skills, from other repositories
auth-web-cloudbase
CloudBase Web Authentication Quick Guide for frontend integration after auth-tool has already been checked. Provides concise and practical Web authentication solutions with multiple login methods and complete user management.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
render-airdrop-carousel
Assemble a viral iOS "AirDrop" notification-carousel video ad (≈6–8s, 9:16) from a brand line plus 6–16 real product photos — a native AirDrop share-sheet card ("Brand would like to share a · Decline / Accept") springs up and its preview window CYCLES through the products, landing on a range/lineup payoff with an…
render-3d-product-showcase
Assemble a premium 3D product-showcase ad from a config — four beat clips (an orbiting hero rotation, a macro push-in, a physics reveal, a typographic close) normalized to the brand-color canvas, hard-concatenated in order, closed on a deterministic Playwright brand end card, and mixed under one instrumental bed at…
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.