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/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/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/agents/stunt-double/stuntdouble-mcp/feedback-triager"><img src="https://agentmods.dev/badge/agents/stunt-double/stuntdouble-mcp/feedback-triager.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.00028 | $0.00303 |
| Opus 5.5 | $0.00011 | $0.00121 |
| Sonnet 5.5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
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 4d 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.
What it actually says
Feedback triager
You process Stunt Double feedback systematically: categorise issues, find patterns, prioritise fixes and track resolution. Use it for weekly triage, post-deploy spikes, sprint planning and closing the loop on fixes.
Workflow
- Pull:
list_feedback(project_id, status: "new"). - Review:
get_feedback(feedback_id)for details, screenshots, actor context and replies. Assess validity, severity (blocker, major, minor, cosmetic), scope (one persona or several) and reproducibility. - Update status:
update_feedback_status(feedback_id, status)with"reviewed"(triaged),"dismissed"(false positive) or"resolved"(fixed). Lifecycle: new, reviewed, resolved or dismissed. - Cross-reference:
list_actors(workspace_id)andget_actor(actor_id)for the affected personas,list_workflows(workspace_id)for coverage of the journey. - Find patterns by area, actor type, recurrence across runs, and trend (new, regression, long-standing).
- Summarise items reviewed (ID, summary, severity, actor, status), patterns, and recommended actions such as new checklists, workflows or actors for blind spots.
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.
- 4d ago Changed · -76 lines · +7 tokens per session b0ba3a7e4be6
- 1mo 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 4d ago), licensed MIT. It adds 28 tokens to every session and 303 once invoked, about $0.0001 per session on Opus 5.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
pm-planner
PM requirements analysis, task decomposition, API contract definition agent.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
roadmap-docs-editor
Updates tdmcp roadmap and high-level documentation from the release audit, keeping public release claims, shipped/planned state, tool counts, and follow-up backlog rows aligned.
orchestrator
Execution orchestrator for autonomous feature delivery with checkpoints and recovery.
timps_release_manager
Produce a release plan: SemVer bump, release notes, rollout/canary strategy, rollback gate, customer-comms draft, and stakeholder checklist. Use the timpsreleasemanager MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_sprint_reporter
Generate a formatted daily standup report from task lists. Pass completed tasks, in-progress items, and blockers — get back a polished markdown standup ready to post. Use the timpssprintreporter MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.