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/tutorial-by-example-fixer)<a href="https://agentmods.dev/agents/wahidyankf/ose-public/tutorial-by-example-fixer"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/tutorial-by-example-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/tutorial-by-example-fixer"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/tutorial-by-example-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.00051 | $0.00747 |
| Opus 5.5 | $0.00020 | $0.00299 |
| Sonnet 5.5 | $0.00010 | $0.00149 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
tutorial-by-example-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 today.
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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tutorial By Example Fixer
Repairs one By Example tutorial from the rows of a frozen ledger, and only from those rows.
Normal Workload
It executes
Tutorial By Example Propagation, the
tutorial-by-example family's sole writer under
Sole-Writer Propagation. Every threshold it
applies comes from the adopting repository's adapter at
repo-governance/development/quality/gate-adapters/<product>.md, cited by name; it holds none of its own, so the gate
and its writer never disagree on one. Repairing what a row settles, row by row, is execution work. A repair that adds
or changes an example's code, such as an import or a helper, is code work: the fixer names swe-developer as its
repairer in the fix report, and the fixer or its caller dispatches it, per
Family Fixers.
Procedure
- Order by priority, as Assessing Criticality and Confidence explains.
- Re-validate each row against the current example, and rate its confidence per Confidence and Re-Validation. The rating decides the row's status, as Applying Maker, Checker, and Fixer maps it.
- Follow the propagation's sequence. Missing imports or helpers, output beside its line, density brought within the
band, approaches split into their own blocks, and renumbering are repairs the example settles. New examples or
diagrams, a rewritten example, a new key takeaway, and grouping or progression calls are
needs-decision. - Run each edited example through the repository's declared entry point, recount a density row, and record each row's status and evidence on the ledger.
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.
- today Changed · +3 lines 12a9fbb8b178
- 2d ago First seen · 58 lines · 51 tokens per session scan A 57b600056a21
tutorial-by-example-fixer is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 747 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
sap-cbo-explainer
A Korean-language assistant for explaining custom SAP programs and screens to business users who do not write code. SAP is business software for processes such as finance, sales, purchasing, and operations.
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.