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.
/plugin marketplace add Rabithua/FeedbackServerPluginnpx agentmods add plugins/rabithua/feedbackserverplugin/feedback-servergit clone --depth 1 https://github.com/Rabithua/FeedbackServerPluginGrade A, and why
feedback-server 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 yesterday.
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
{
"name": "feedback-server",
"version": "1.2.1",
"description": "Authenticate and manage FeedbackKit products, feedback, waitlists, activity, roadmaps, releases, and notifications through MCP.",
"author": {
"name": "Rabithua",
"url": "https://github.com/Rabithua"
},
"homepage": "https://github.com/Rabithua/FeedbackServerPlugin",
"repository": "https://github.com/Rabithua/FeedbackServerPlugin",
"license": "MIT",
"keywords": [
"feedback",
"waitlist",
"roadmap",
"changelog",
"mcp",
"oauth"
],
"skills": [
"./skills/setup-feedback-server",
"./skills/triage-feedback",
"./skills/manage-waitlist",
"./skills/publish-roadmap-releases",
"./skills/configure-notifications",
"./skills/administer-feedback-server",
"./skills/manage-feedback-server"
]
}
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.
- yesterday First seen · 30 lines scan A 8df20f39dea1
feedback-server is a plugin published in the GitHub repository Rabithua/FeedbackServerPlugin (0 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
feedback-studio
Plugin marketplace listing 1 plugin: feedback-studio.
feedback-studio
A local commenting overlay for a website you're building (a static build or your local dev server) or a Markdown file, not public sites you browse. Click or tap any element (or select text) and leave typed or spoken feedback; comments persist to .feedback/, then you tell your agent 'PPF' (Please Process Feedback) to…
cc-htmlfeedback
Live in-browser feedback loop for local web pages: serve a page with a comment widget injected, then turn the comments you leave into fix-it tickets Claude Code applies and verifies in place.
cc-htmlfeedback
Plugin marketplace listing 1 plugin: cc-htmlfeedback.
paydirt-plugins
Official Paydirt plugins for agent-installed iOS feedback.
paydirt
Install and operate Paydirt feedback, cancellation, and Slack workflows in iOS apps.