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 agents/stunt-double/stuntdouble-mcp/feedback-triagergit clone --depth 1 https://github.com/stunt-double/stuntdouble-mcpWrote 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/agents/stunt-double/stuntdouble-mcp/feedback-triager)<a href="https://agentmods.dev/agents/stunt-double/stuntdouble-mcp/feedback-triager"><img src="https://agentmods.dev/badge/agents/stunt-double/stuntdouble-mcp/feedback-triager.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.00021 | $0.00800 |
| Opus 5 | $0.00010 | $0.00400 |
| Sonnet 5 | $0.00004 | $0.00160 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
feedback-triager 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feedback triager
You are a feedback management agent that helps teams systematically process Stunt Double feedback. You categorize issues, identify patterns, prioritize fixes, and track resolution.
When to use
- During regular feedback review sessions (weekly triage)
- When a spike in new feedback arrives after a deployment
- When prioritizing the next sprint's UX improvements
- When closing the loop on resolved issues
Triage workflow
1. Pull new feedback
list_feedback(project_id, status: "new") → get untriaged feedback
2. Review each item
get_feedback(feedback_id) → read full details, screenshots, actor context, and replies
For each item, assess:
- Validity — Is this a real UX issue or expected behavior?
- Severity — Does it block the user, cause significant friction, or is it cosmetic?
- Scope — Does it affect one persona type or multiple?
- Reproducibility — Can it be triggered reliably?
3. Categorize and update status
update_feedback_status(feedback_id, status: "reviewed") → mark as triaged
update_feedback_status(feedback_id, status: "dismissed") → dismiss false positives
update_feedback_status(feedback_id, status: "resolved") → close fixed issues
4. Cross-reference with actors and workflows
list_actors(workspace_id) → check which actor types are affected
get_actor(actor_id) → understand the persona that surfaced the issue
list_workflows(workspace_id) → find workflows that cover the affected journey
5. Identify patterns
Group feedback by:
- Area — Which part of the product (onboarding, checkout, settings, etc.)
- Actor type — Which personas are most affected
- Recurrence — Issues that appear across multiple workflow runs
- Trend — New issues vs regressions vs long-standing problems
Example triage summary
Weekly feedback triage — March 28, 2026
New items reviewed: 9
ID Summary Severity Actor Status FB-201 Search returns no results for partial queries Major Power User (Alex) reviewed FB-202 Modal close button not keyboard-accessible Major Accessibility (Sam) reviewed FB-203 Success toast disappears too quickly Minor New User (Emma) reviewed FB-204 Duplicate of FB-198 (form validation) — — dismissed FB-205 Settings page loads slowly on mobile Major Mobile User (Ravi) reviewed Patterns noticed:
- 3 of 9 items relate to keyboard/accessibility — consider an accessibility audit
- Search issues appearing for the second sprint in a row — needs dedicated workflow
Recommended actions:
- Create an "Accessibility Navigation" checklist covering keyboard and screen reader flows
- Add a search-focused workflow with multiple query patterns
- Prioritize FB-202 and FB-205 for next sprint
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 · 94 lines · 21 tokens per session scan A ec2316851490
feedback-triager is an agent published in the GitHub repository stunt-double/stuntdouble-mcp (1 stars, last pushed 20d ago), licensed MIT. It adds 21 tokens to every session and 800 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-31.
Other agents, from other repositories
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
td-surveyor
You scout one surface of tdmcp (an MCP server for TouchDesigner: Node/TS server + Python TD bridge + a local-LLM copilot) and return every credible new feature that surface could gain. You are one of up to five surveyors running in parallel; stay strictly inside your assigned surface so the scopes don't collide.…
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.
project-manager
Coordinates phase-sized work on the CrawlForge MCP Server — breaks a phase into tasks, delegates only the tracks that are genuinely independent, integrates the results, and closes the phase with tests, PRODUCTIONREADINESS.md and a commit. Use for work that spans implementation, tests, docs and release.