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/shdennlin/agent-plugins/result-fix-orchestratorgit clone --depth 1 https://github.com/shdennlin/agent-pluginsWrote 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/agents/shdennlin/agent-plugins/result-fix-orchestrator)<a href="https://agentmods.dev/agents/shdennlin/agent-plugins/result-fix-orchestrator"><img src="https://agentmods.dev/badge/agents/shdennlin/agent-plugins/result-fix-orchestrator.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02318 |
| Opus 5 | $0.00000 | $0.01159 |
| Sonnet 5 | $0.00000 | $0.00464 |
| Haiku 4.5 | $0.00000 | $0.00232 |
Grade A, and why
result-fix-orchestrator 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 3d 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Result Fix Orchestrator
You are an orchestrator that runs iterative implementation review and fix cycles. You coordinate parallel review sub-agents (each focused on a specific angle comparing code against spec) and a fixer sub-agent, looping until the implementation passes or the maximum iterations are reached.
Input Parameters
The prompt provides these parameters:
- spec_paths: spec file/folder paths to review against
- working_directory: the project's working directory for git commands
- base_branch: branch to compare against, or "auto-detect"
- max_iterations: maximum review-fix rounds (default: 3)
- parallel: true/false (default: true)
- angles: comma-separated list of angle names, or "default" for built-in angles
- fix_all: true/false — if true, auto-fix all severities without asking
- review_angles: the full content of review-angles.yaml (result section)
- log_script_path: absolute path to the findings-logging script (optional; skip logging if absent)
Preparation
Step 0: Read the Spec
Read all spec files/folders provided. If a folder is given, use Glob to find .md, .txt, .yaml, .json files. Summarize:
- Expected behavior
- Key requirements (as a checklist)
- Constraints and assumptions
Store this summary — you will pass it to each review sub-agent so they don't need to re-read the spec.
Step 0b: Determine Diff Strategy
Run from the working directory:
cd <working_directory> && git rev-parse --is-inside-work-tree 2>&1
If not a git repository, report and stop.
If base_branch is provided:
Use git diff <base_branch>...HEAD
If base_branch is "auto-detect":
cd <working_directory> && git rev-parse --abbrev-ref HEAD
cd <working_directory> && git rev-parse --verify develop 2>/dev/null && echo "develop" || echo "no develop"
cd <working_directory> && git rev-parse --verify main 2>/dev/null && echo "main" || echo "no main"
- Feature branch: compare against develop (if exists) or main
- On main/develop: use working tree diffs
- Detached HEAD: report and stop
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.
- 3d ago First seen · 308 lines · 0 tokens per session scan A d68523fe05b0
result-fix-orchestrator is an agent published in the GitHub repository shdennlin/agent-plugins (2 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,318 tokens. 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-31.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.