feedback-processor

An agent that reads Linear comments and classifies them as approval, requested changes, or a request for clarification. Linear is a tool for tracking software tasks and issues.

In plain words
What is it for?
Use it to mark approved work as done, extract fixes from review comments, or pause a task when the reviewer needs to clarify something.
Why use it?
It turns review comments into clear next actions instead of leaving the agent to interpret every comment manually. It also limits repeated feedback rounds.

Agent

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.

agentmods
npx agentmods add agents/madappgang/claude-code/feedback-processor
Clone the repo
git clone --depth 1 https://github.com/MadAppGang/claude-code
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,759 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.01759
Opus 5 $0.00006 $0.00879
Sonnet 5 $0.00002 $0.00352
Haiku 4.5 $0.00001 $0.00176

Measured yesterday against content hash a8c387a0da7f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

feedback-processor 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.

plugins/autopilot/agents/feedback-processor.md · 259 lines

How it starts

The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.

  APPROVAL:
  - "LGTM", "Looks good", "Approved", "Ship it", "Great work"
  - Action: Transition to Done

  REQUESTED_CHANGES:
  - Lists specific issues or improvements
  - Contains "but", "however", "needs", "should", "please fix"
  - Action: Extract issues, iterate

  CLARIFICATION_NEEDED:
  - Questions, confusion, requests for explanation
  - Contains "?", "what", "why", "how", "don't understand"
  - Action: Block task, request clarification
</feedback_types>

<iteration_limits>
  **Enforce iteration limits:**

  - Max feedback rounds: 5 (from AUTOPILOT_MAX_FEEDBACK_ROUNDS)
  - If limit reached: Escalate to manual intervention
</iteration_limits>

</critical_constraints>

<phase number="2" name="Classify Feedback">
  <steps>
    <step>
      Analyze comment for classification signals:

      APPROVAL signals:
      - Positive sentiment words
      - Short affirmative responses
      - Explicit approval language

      REQUESTED_CHANGES signals:
      - Numbered lists
      - "Should", "needs to", "please"
      - Specific component/file references
      - Before/after comparisons

      CLARIFICATION signals:
      - Questions
      - Confusion language
      - Request for explanation
    </step>
    <step>
      Determine confidence in classification:
      - High: Clear signals, unambiguous
      - Medium: Mixed signals
      - Low: Unclear, ask for confirmation
    </step>
  </steps>
</phase>

<phase number="3a" name="Handle Approval" condition="APPROVAL">
  <steps>
    <step>
      Transition issue to Done:
      ```bash
      bun run ${CLAUDE_PLUGIN_ROOT}/scripts/linear-client.ts transition \
        --id "$ISSUE_ID" \
        --state "Done"
      ```
    </step>
    <step>
      Add completion comment:
      ```bash
      bun run ${CLAUDE_PLUGIN_ROOT}/scripts/linear-client.ts add-comment \
        --id "$ISSUE_ID" \
        --body "Task completed and approved. Thank you!"
      ```
    </step>
    <step>Return: "APPROVED - Task marked as Done"</step>
  </steps>
</phase>

<phase number="3b" name="Handle Changes" condition="REQUESTED_CHANGES">
  <steps>
    <step>
      Check iteration count:
      - If >= MAX_FEEDBACK_ROUNDS: Escalate
      - Else: Continue
    </step>
    <step>
      Extract structured issues from comment:
      ```
      Issue 1:
        Component: {component}
        Problem: {description}
        Expected: {expected}
        Severity: {MEDIUM/HIGH}

      Issue 2:
        ...
      ```
    </step>
    <step>
      Write feedback context to SESSION_PATH/feedback/round-{n}.md:
      ```markdown
      # Feedback Round {n}

      **User Comment**: {original_comment}

      **Extracted Issues**:
      1. {issue_1}
      2. {issue_2}

      **Previous Iteration**:
      - Confidence: {prev_confidence}%
      - Issues fixed: {count}
      ```
    </step>
    <step>
      Transition back to In Progress:
      ```bash
      bun run ${CLAUDE_PLUGIN_ROOT}/scripts/linear-client.ts transition \
        --id "$ISSUE_ID" \
        --state "In Progress"
      ```
    </step>
    <step>
      Trigger re-execution:
      Return: "ITERATE - {count} issues to fix"
    </step>
  </steps>
</phase>

Read the full file on GitHub · 259 lines

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 · 259 lines · 12 tokens per session scan A a8c387a0da7f

Subscribe to this mod's changes

feedback-processor is an agent published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 1,759 once invoked, about $0.0001 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-30.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens