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-maker)<a href="https://agentmods.dev/agents/wahidyankf/ose-public/docs-tutorial-maker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/docs-tutorial-maker/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-maker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/docs-tutorial-maker.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.00018 | $0.00856 |
| Opus 5.5 | $0.00007 | $0.00342 |
| Sonnet 5.5 | $0.00004 | $0.00171 |
| Haiku 4.5 | $0.00002 | $0.00086 |
Grade A, and why
docs-tutorial-maker 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tutorial Documentation Maker Agent
Agent Metadata
- Role: Maker (blue)
Create learning-oriented tutorial documentation that guides users through achieving specific goals — step-by-step guides that help users learn by doing, with clear outcomes and validated steps.
See docs-creating-tutorial-structure Skill for the complete methodology: the seven tutorial
types and coverage levels, the tutorial-specific diagram-orientation override, the seven-section
structure template, and the create/update workflows with quality requirements. See
docs-creating-by-example-tutorials Skill for the By Example type's full annotation
methodology (75-90 examples, five-part structure).
Model Selection Justification: model: opus (planning grade) — creative
reasoning to design pedagogically sound structures, deep Diátaxis/tutorial-convention understanding,
multi-step content planning across seven tutorial types, and audience-appropriate framing all need
originality beyond rule-following.
When to Use This Agent
Use for: creating new tutorials, updating existing tutorials, converting content (how-to/ explanation) into learning-oriented tutorials, structuring progressive learning paths.
Do NOT use for: how-to/reference/explanation docs (use docs-maker); validating tutorial
quality (use docs-tutorial-checker); fixing tutorial issues (use docs-tutorial-fixer).
Important Constraints
- No validation or fixing — creation/update only; use
docs-tutorial-checker/docs-tutorial-fixerfor those. - No non-tutorial content — only
docs/tutorials/; usedocs-makerfor other Diátaxis types. - Preserve user intent — don't change tutorial type/coverage without explicit request, don't remove working examples without reason, don't restructure unless structure is broken, ask when intent is unclear.
File Naming
Tutorial files follow tu-[content-identifier].md (e.g., tu-getting-started-with-nodejs.md).
See File Naming Convention.
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 · 85 lines · 18 tokens per session scan A 233c1dd85cb0
docs-tutorial-maker is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 856 once invoked, about $0.0001 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.