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 baskb/feedback-studionpx agentmods add plugins/baskb/feedback-studio/marketplacegit clone --depth 1 https://github.com/baskb/feedback-studioGrade A, and why
feedback-studio 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-studio",
"metadata": {
"description": "Local visual feedback overlay for a site you're building or a Markdown file. Click or tap any element (or select text), leave typed or spoken feedback, then tell your agent 'PPF' (Please Process Feedback) to apply it."
},
"owner": {
"name": "Bastiaan Kortenbout"
},
"plugins": [
{
"name": "feedback-studio",
"source": "./plugins/feedback-studio",
"version": "1.0.0",
"description": "Click or tap any element on any local page and leave typed or spoken feedback; comments persist to .feedback/, then tell your agent 'PPF' (Please Process Feedback) to apply them. Static build or dev-server proxy; phone review by voice over a Cloudflare tunnel (--tunnel) or self-signed HTTPS.",
"category": "productivity",
"keywords": [
"feedback",
"review",
"comments",
"overlay",
"voice"
]
}
]
}
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 · 26 lines scan A 6a47e1339b4d
feedback-studio is a plugin published in the GitHub repository baskb/feedback-studio (2 stars, last pushed 5d 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
scaccogatto
Claude Code plugins by scaccogatto.
prd-os
PRD operating system: capture rough ideas, draft reviewable PRDs, run standard and adversarial review (Codex or a Claude senior-staff-engineer subagent, recorded truthfully), triage findings, decompose approved PRDs into atomic issue specs, and execute those issues with scope enforcement, stop-gate receipts, and…
spacedock
Turn directories of markdown files into structured workflows operated by AI agents.
scraps-migration
LLM migration workflows for moving Scraps wikis from v0 to v1. Runs version-pinned audits, converts tag and config syntax, and verifies the result with v1 lint/build.
callee
Plugin marketplace listing 1 plugin: callee.
onebrain
OneBrain — Your AI Thinking Partner.