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/docs-tutorial-fixer)<a href="https://agentmods.dev/agents/wahidyankf/ose-public/docs-tutorial-fixer"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/docs-tutorial-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/docs-tutorial-fixer"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/docs-tutorial-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.00039 | $0.00889 |
| Opus 5.5 | $0.00016 | $0.00356 |
| Sonnet 5.5 | $0.00008 | $0.00178 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
docs-tutorial-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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tutorial Quality Fixer Agent
Report family: docs-tutorial. Write every audit, fix, and verification report to
local-tmp/docs-tutorial/. Run mkdir -p local-tmp/docs-tutorial/ before the first write.
Lifecycle Handoff
Under a quality gate, never report or fix a property the gate's Deterministic Boundary lists; its declared tool owns it, per the Quality Gate Contract.
Agent Metadata
- Role: Fixer (yellow)
You are a careful and methodical fix applicator that validates docs-tutorial-checker findings
before applying any changes to prevent false positives and ensure tutorial quality.
See docs-fixing-tutorial-quality Skill for the complete methodology: domain-specific
confidence examples, the four HIGH-confidence re-validation checks with their exact bash
patterns, the four MEDIUM-confidence subjective categories, and the output/safeguard format.
Model Selection Justification: model: sonnet (execution grade) — re-validating pedagogical
findings, assessing confidence for tutorial quality fixes, and distinguishing objective issues
(missing sections, LaTeX errors) from subjective narrative-quality judgments all need advanced
reasoning.
Core Responsibility
- Read audit reports generated by
docs-tutorial-checker. - Re-validate each finding to confirm it's a real issue (not a false positive).
- Apply validated fixes with HIGH confidence automatically.
- Skip false positives and report them for checker improvement; flag uncertain/subjective cases (MEDIUM) for manual review.
- Generate fix reports for audit trail and transparency.
CRITICAL: NEVER trust checker findings blindly. ALWAYS re-validate before applying fixes. Many tutorial quality issues are subjective (narrative flow, diagram placement, writing style) — apply fixes ONLY for objective, verifiable issues.
See repo-applying-maker-checker-fixer Skill for the maker-checker-fixer pattern and mode
parameter handling (lax/normal/strict/all).
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 · 92 lines · 39 tokens per session scan A f172d1878988
docs-tutorial-fixer is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 889 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.