Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add paulbaranowski/wild-horses/plugin install harnessWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/paulbaranowski/wild-horses/feedback-blockers)<a href="https://agentmods.dev/commands/paulbaranowski/wild-horses/feedback-blockers"><img src="https://agentmods.dev/badge/commands/paulbaranowski/wild-horses/feedback-blockers/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/paulbaranowski/wild-horses/feedback-blockers"><img src="https://agentmods.dev/badge/commands/paulbaranowski/wild-horses/feedback-blockers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00078 | $0.02859 |
| Opus 5 | $0.00039 | $0.01430 |
| Sonnet 5 | $0.00016 | $0.00572 |
| Haiku 4.5 | $0.00008 | $0.00286 |
Grade A, and why
feedback-blockers 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 9d ago.
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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feedback Blockers Review
Analyze code for feedback-loop blockers — encapsulation gaps, OOP design issues, testability barriers, and harness-unfriendly patterns that prevent fast, clear change-test-fix cycles. Uses 4 parallel specialist agents, then synthesizes findings into a prioritized remediation plan with concrete interventions.
Bundled assets at ${CLAUDE_PLUGIN_ROOT} (if the variable isn't substituted in this context, find the files with Glob "**/harness/loop-protocol.md" and read the siblings alongside it):
loop-protocol.md— Phase 4 options menu. Shared with/harness:reasoning-gaps.task-list-schema.md— JSON task file shape. Shared with/harness:reasoning-gaps,task-list-builder, andtask-list-runner.skills/task-list-builder/SKILL.md— task-list construction (verifySteps discovery, run-ID, JSON + MD writing, preview). Invoked from Phase 4 Options 1, 2, and 3 with--slug feedback-blockers --md-body-from-context.skills/task-list-runner/SKILL.md— execution engine (resume, Agent loop, Task Implementation Prompt). Invoked from Phase 4 Options 1 and 2 and from--resume.agents/feedback-blockers/encapsulation.mdagents/feedback-blockers/oop-design.mdagents/feedback-blockers/testability.mdagents/feedback-blockers/harness-friendliness.md
Target: "$ARGUMENTS"
Slug: feedback-blockers (use this value wherever loop-protocol.md says <slug>).
Resume Check (before Phase 1)
If $ARGUMENTS contains --resume, hand off to the task-list-runner skill (it will auto-locate the in-progress task file or accept a path that follows --resume). Skip Phases 1–4 entirely.
Phase 1: Determine Scope (you do this)
Based on arguments and context, determine what files to analyze:
- If a specific file/directory path is given — collect those file paths.
- If a free-form description is given (e.g., "the cli code", "the decoder pipeline", "authentication logic") — search the codebase to identify matching files. Use directory names, module names, class/function names, and file contents to resolve the description to a concrete list of files. Confirm the resolved scope with the user if ambiguous.
- If no arguments (DEFAULT) — get only the files changed in the current PR branch:
git diff --name-only main...HEADplus any uncommitted changes viagit diff --name-only. Exclude test files and non-source files. This should typically yield 3–10 files. If it yields more than 15, ask the user to narrow scope. - If
--full— collect all source files insrc/or the main package directory (warn: may be slow).
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.
- 9d ago First seen · 172 lines · 78 tokens per session scan A 1ce37e0fd31f
feedback-blockers is a command published in the GitHub repository paulbaranowski/wild-horses (12 stars, last pushed 21d ago), licensed MIT. It adds 78 tokens to every session and 2,859 once invoked, about $0.0004 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 commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.