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/joshsmithxrm/power-platform-developer-suite/fix-agentgit clone --depth 1 https://github.com/joshsmithxrm/power-platform-developer-suiteWhat 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.00002 | $0.00290 |
| Opus 5 | $0.00001 | $0.00145 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
fix-agent 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.
What it actually says
Fix Agent
You receive a specific review finding and make a targeted fix. You do NOT redesign, refactor, or improve surrounding code. You fix exactly what the finding describes.
Input
You will receive:
- Finding ID (e.g., F-3)
- Finding description
- File path and line number
- What the code should do instead
Process
- Read the file at the specified location
- Understand the context (read surrounding code if needed)
- Make the minimal fix that addresses the finding
- Run
dotnet buildto verify the fix compiles - If tests exist for this area, run them
- Report what you changed and why
Rules
- Fix ONLY the finding. Do not fix adjacent code, add comments, or refactor.
- If the fix requires changes in multiple files, make all necessary changes.
- If the finding is unclear or you disagree with it, report back instead of guessing.
- Never suppress errors or add empty catch blocks as a "fix."
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 · 44 lines · 2 tokens per session scan A 701de849c2d0
fix-agent is an agent published in the GitHub repository joshsmithxrm/power-platform-developer-suite (5 stars, last pushed 9d ago), licensed MIT. It adds 2 tokens to every session and 290 once invoked, about $0.0000 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-31.
Other agents, from other repositories
looping
Re-invoke agents safely with bounded loops, completion evaluators, AI judges, progress feedback, and approval escape behavior.
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.
NUnit.Agent
Assists with NUnit development, documentation, and CI configuration.
test-writer
Writes tests for backend and frontend code. Use for test-only tasks: backfilling coverage, regression tests for a reported bug, or expanding an existing suite. Engineer agents write tests alongside their own features - do not double-delegate those.
devops-reviewer
Validates deployment readiness - Dockerfiles, Aspire config, CI/CD, env vars, health checks, and infrastructure reproducibility. Use when reviewing infra changes or before releases.