A feedback hub for coding agents that combines a feedback queue with project-specific message connections. It supports Claude Code, Codex, and Gemini through each tool's configuration and instruction files.

Use it to connect an agent project to a tagged feedback bus and process feedback items through the loopback skill.

It gives agents a shared place to receive and work through project feedback instead of keeping feedback in separate tool-specific workflows.

loopback — Plugin by joshidikshant

Install

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.

Claude Code

/plugin marketplace add joshidikshant/loopback

agentmods

npx agentmods add plugins/joshidikshant/loopback/plugin

Clone the repo

git clone --depth 1 https://github.com/joshidikshant/loopback

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

loopback 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.

plugin/.claude-plugin/plugin.json · 19 lines

What it actually says

{
  "name": "loopback",
  "version": "0.9.4",
  "description": "Loopback feedback hub for Claude Code: the loopback skill (work the feedback queue) + MCP registration for the project-tagged feedback bus. Codex gets the same via .agents/skills + config.toml; Gemini via AGENTS.md + settings.json.",
  "author": {
    "name": "Dikshant Joshi",
    "url": "https://github.com/joshidikshant"
  },
  "homepage": "https://github.com/joshidikshant/loopback",
  "repository": "https://github.com/joshidikshant/loopback",
  "license": "MIT",
  "keywords": [
    "feedback",
    "mcp",
    "queue",
    "agents"
  ]
}

Changes

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 · 19 lines scan A 6e6187541e6a

Subscribe to this mod's changes

loopback is a plugin published in the GitHub repository joshidikshant/loopback (0 stars, last pushed 1mo 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.

ai-agents claude-code codex coding-agents developer-tools devtools

loopback

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

agent-harness-skills

coder-eval

jenkins-cli

deslop

infino-ai

rudder