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/unbounce/agent-plugins/mcp-feedbacknpx skills add unbounce/agent-plugins --skill mcp-feedbackgit clone --depth 1 https://github.com/unbounce/agent-pluginsWrote 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/unbounce/agent-plugins/mcp-feedback)<a href="https://agentmods.dev/skills/unbounce/agent-plugins/mcp-feedback"><img src="https://agentmods.dev/badge/skills/unbounce/agent-plugins/mcp-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.00146 | $0.01117 |
| Opus 5 | $0.00073 | $0.00558 |
| Sonnet 5 | $0.00029 | $0.00223 |
| Haiku 4.5 | $0.00015 | $0.00112 |
Grade A, and why
mcp-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 3d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submit Unbounce MCP feedback
Record the user's feedback about the Unbounce MCP tools to the team's store by
calling the submit_feedback tool. The tool persists the record server-side, so
nothing has to be copied out of the conversation into Slack or anywhere else.
The
mcp-prefix here means "pertains to Unbounce MCP," not "about a page." This skill is about capturing feedback on the MCP tools themselves — whether they broke, delighted, confused, or fell short.
Hard rule: report, don't repair
Do NOT try to fix, retry, or work around the thing being reported. This skill
records feedback on what already happened. Never invent tool-call arguments or error
text — anything not actually present is unknown. (Fixing the underlying task, if the
user wants that, is separate work done after the feedback is recorded.)
1. Gather the feedback
Settle two things — from the conversation where possible, asking only what you can't infer:
type— one ofbug·praise·feature_request·confusion·other.message— the feedback in the user's own words. Keep it faithful; don't editorialize.
For a bug, also assemble the context: the verbatim failing tool call(s)
from the transcript — exact tool name, exact arguments JSON, and the raw result/error
text (call out any code/reason/remedy fields). Include the relevant one(s),
especially the failing call. If the failure happened in another session and isn't in
the transcript, ask a couple of targeted questions and mark transcript-only fields
(exact arguments, exact raw error) as unknown. For non-bug types, context is
usually unnecessary — include a light pointer (the tool or page in question) only if
it genuinely helps.
Login / connection problems are a bug: capture what the user was doing, the
client they're in, and the exact error text (e.g. access denied, invalid_grant, a
failed redirect, repeated re-login prompts). Note that if the MCP can't connect at
all, submit_feedback itself won't be reachable — that's expected, and step 4's
inline fallback is how the feedback still gets out.
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.
- 3d ago First seen · 88 lines · 146 tokens per session scan A 020e579eeb7b
mcp-feedback is a skill published in the GitHub repository unbounce/agent-plugins (1 stars, last pushed 7d ago), licensed MIT. It adds 146 tokens to every session and 1,117 once invoked, about $0.0007 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
landing-page-creator
Build high-converting affiliate landing pages as single self-contained HTML files. Triggers on: "create a landing page for", "build a landing page", "product landing page", "affiliate landing page", "comparison page for", "vs page", "single product page", "conversion page", "sales page for affiliate", "landing page…
product-showcase-page
Build a single-product deep-dive showcase page as a self-contained HTML file. Triggers on: "build a product showcase page", "deep dive landing page for [product]", "create a product spotlight page", "product feature page", "single product page", "detailed page about [product]", "build a page showing everything about…
webinar-registration-page
Build a webinar or live event registration page as a self-contained HTML file with countdown timer, speaker bio, agenda, and registration form. Triggers on: "build a webinar registration page", "create a webinar sign-up page", "event registration landing page", "live training registration page", "workshop sign-up…
grand-slam-offer
Design irresistible affiliate offers using the Hormozi Grand Slam framework. Triggers on: "create an offer for", "design my offer", "grand slam offer", "make an irresistible offer", "why should someone buy through my link", "offer framework", "value proposition for", "Hormozi offer", "offer stack", "make my offer…
squeeze-page-builder
Build email capture landing pages (squeeze pages) as single self-contained HTML files. Triggers on: "build a squeeze page", "email capture page", "lead magnet page", "create an opt-in page", "build an email list page", "lead capture landing page", "create a freebie page", "build a page to collect emails", "opt-in…
bonus-stack-builder
Design exclusive bonus packages that make YOUR affiliate link the obvious choice. Triggers on: "create bonuses for", "bonus stack", "what bonuses should I offer", "bonus ideas for", "exclusive bonuses", "differentiate my affiliate link", "why buy through my link", "affiliate bonuses", "bonus package", "what can I…