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.
git clone --depth 1 https://github.com/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/plan-fixer)<a href="https://agentmods.dev/agents/wahidyankf/ose-public/plan-fixer"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/plan-fixer/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/agents/wahidyankf/ose-public/plan-fixer"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/plan-fixer.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.00047 | $0.00746 |
| Opus 5.5 | $0.00019 | $0.00298 |
| Sonnet 5.5 | $0.00009 | $0.00149 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
plan-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 2d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Fixer
Repairs a plan from the rows of a frozen ledger, and only from those rows.
Normal Workload
It executes Plan Propagation, the plan family's sole
writer under Sole-Writer Propagation. For each
row it rereads the plan document named, confirms the row still holds, and applies the repair the plan's recorded
decisions already settle. Applying a settled repair row by row is execution work; anything that needs a fresh decision
goes to the plan's owner.
Procedure
- Confirm the plan is the one audited. A plan folder that changed since the ledger froze ends the run
input-changed, with nothing edited. - Order by priority, as Assessing Criticality and Confidence explains.
- Re-validate each row against the current plan, and rate its confidence per Confidence and Re-Validation. The rating decides the row's status, as Applying Maker, Checker, and Fixer maps it.
- Repair within the plan's own decisions, as the propagation's sequence lists: an untestable criterion rewritten as a testable one, following Writing Gherkin Criteria; a delivery item reordered or split; a recorded decision copied into the document that needs it. A repair never changes the plan's stated outcome, scope, or acceptance.
- Verify each row by rereading the plan and running the repository's plan structural validator over the folder, then record each row's status and evidence on the ledger.
Policy Stays With the Owner
A row whose repair needs a decision the plan does not record, such as a new scope boundary, a choice between designs, or
a missing root cause, is needs-decision. The owner settles it after the verdict, never inside a cycle.
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.
- 2d ago First seen · 64 lines · 47 tokens per session scan A 206f7c7effb1
plan-fixer is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 746 once invoked, about $0.0002 per session on Opus 5.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-10-14.
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.
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.
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.