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/reasoning-gaps)<a href="https://agentmods.dev/commands/paulbaranowski/wild-horses/reasoning-gaps"><img src="https://agentmods.dev/badge/commands/paulbaranowski/wild-horses/reasoning-gaps/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/reasoning-gaps"><img src="https://agentmods.dev/badge/commands/paulbaranowski/wild-horses/reasoning-gaps.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.00073 | $0.03699 |
| Opus 5 | $0.00036 | $0.01850 |
| Sonnet 5 | $0.00015 | $0.00740 |
| Haiku 4.5 | $0.00007 | $0.00370 |
Grade A, and why
reasoning-gaps 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 10d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Reasoning Gap Analysis
Analyze code for AI reasoning gaps — places where an AI agent cannot confidently trace data flow, predict runtime behavior, or orient itself in the codebase. Uses 3 parallel specialist agents, then synthesizes findings into a prioritized remediation plan with concrete interventions.
This is NOT a code quality review. Code can be well-written and still be opaque to AI reasoning. This skill answers: "If an AI agent read this code, what would it get wrong?"
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:feedback-blockers.task-list-schema.md— JSON task file shape. Shared with/harness:feedback-blockers,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 reasoning-gaps --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/reasoning-gaps/types-and-data-contracts.mdagents/reasoning-gaps/implicit-flow-and-state.mdagents/reasoning-gaps/structure-and-documentation.md
Target: "$ARGUMENTS"
Slug: reasoning-gaps (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. 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.
- 10d ago First seen · 197 lines · 73 tokens per session scan A fb9a0d4facdf
reasoning-gaps is a command published in the GitHub repository paulbaranowski/wild-horses (12 stars, last pushed 22d ago), licensed MIT. It adds 73 tokens to every session and 3,699 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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.