bug-echo

A debugging helper that looks for other places where the same bug pattern may appear after you fix one instance.

In plain words
What is it for?
Use it for a post-fix code sweep: inspect related matches and separate likely bugs from cases that are safe or need human review.
Why use it?
It reduces the chance that a repeated coding mistake remains elsewhere. It checks the pattern against the original file and labels each possible match for review.

Plugin for Claude Code

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 Terryc21/bug-echo
agentmods
npx agentmods add plugins/terryc21/bug-echo/marketplace
Clone the repo
git clone --depth 1 https://github.com/Terryc21/bug-echo

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

bug-echo 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.

.claude-plugin/marketplace.json · 23 lines

What it actually says

{
  "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  "name": "bug-echo",
  "description": "Find sibling instances of a bug you just fixed. Third stage of the post-fix sweep workflow.",
  "owner": {
    "name": "Terry Nyberg"
  },
  "plugins": [
    {
      "name": "bug-echo",
      "version": "1.6.0",
      "source": "./",
      "description": "After fixing a bug, finds and rates other instances of the same anti-pattern. Self-validates the constructed pattern against the pre-fix file before scanning. Each match is classified individually as BUG / WATCH / OK / REVIEW.",
      "author": {
        "name": "Terry Nyberg"
      },
      "homepage": "https://github.com/Terryc21/bug-echo",
      "license": "Apache-2.0",
      "category": "debugging"
    }
  ]
}
Files

What ships with it

1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. yesterday First seen · 23 lines scan A f715a50014e5

Subscribe to this mod's changes

bug-echo is a plugin published in the GitHub repository Terryc21/bug-echo (23 stars, last pushed 3d ago), licensed Apache-2.0. 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-30.