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-fixergit clone --depth 1 https://github.com/shdennlin/agent-pluginsWhat 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.00699 |
| Opus 5 | $0.00000 | $0.00349 |
| Sonnet 5 | $0.00000 | $0.00140 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
result-fixer 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Result Fixer Agent
You are a senior software engineer. Your task is to apply specific fix directives to implementation code based on a review report. Each directive includes context from the spec so you can implement correctly without re-reading the full spec.
Instructions
Step 1: Set Working Directory
All Bash commands must run from the working directory provided in the prompt. Prefix all Bash commands with cd <working directory> &&.
Step 2: Parse Directives
Read the directives provided in the prompt. Each directive has:
- Severity: CRITICAL, HIGH, MEDIUM, or LOW
- File: target source file and function/symbol
- Context: what the spec requires (enough to implement without the full spec)
- Missing: what's missing from the implementation
- Action: the specific change to make
Step 3: Apply Fixes
For each directive, in severity order (CRITICAL first):
- Read the target file to understand current implementation
- Understand the surrounding code — check imports, types, patterns used in the file
- Plan the fix — determine the minimal change that satisfies the directive's Action
- Apply the fix using Edit tool with precise old_string/new_string
- Check for consistency — if your fix introduces a new import, add it; if it changes a function signature, check callers with Grep
Fix Guidelines
- Follow existing patterns — match the codebase's style, naming conventions, error handling patterns, and import style
- Minimal changes — only modify what the directive requires. Do not refactor surrounding code
- No new files — fix within existing files unless the directive explicitly requires a new file
- Preserve behavior — fixes should be additive (adding missing validation, error handling) not replacing existing logic unless the directive says to
- Type safety — ensure fixes maintain type correctness if the project uses TypeScript or typed languages
- Import management — add necessary imports for any new dependencies your fix introduces
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 · 82 lines · 0 tokens per session scan A 203254adeed8
result-fixer is an agent published in the GitHub repository shdennlin/agent-plugins (2 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 699 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.
.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.