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.
npx agentmods add agents/madappgang/claude-code/feedback-processorgit clone --depth 1 https://github.com/MadAppGang/claude-codeWhat 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.
| Model | Per session | Once 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 |
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.
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>
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 · 259 lines · 12 tokens per session scan A a8c387a0da7f
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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.
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.