OpenMAIC is a multi-agent classroom platform that uses agents to plan, build, and revise interactive courses from prompts and uploaded materials. It is designed for immersive learning experiences and supports course components such as slides, quizzes, interactives, projects, images, video, voices, and PowerPoint imports, with catalogue skills covering its workflows.
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 skills add THU-MAIC/OpenMAIC --skill stage-designgit clone --depth 1 https://github.com/THU-MAIC/OpenMAICWrote 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/skills/thu-maic/openmaic/stage-design)<a href="https://agentmods.dev/skills/thu-maic/openmaic/stage-design"><img src="https://agentmods.dev/badge/skills/thu-maic/openmaic/stage-design.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00097 | $0.01324 |
| Opus 5 | $0.00048 | $0.00662 |
| Sonnet 5 | $0.00019 | $0.00265 |
| Haiku 4.5 | $0.00010 | $0.00132 |
Grade A, and why
stage-design 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building one stage
A stage is one classroom: one settled plan, one roster, one deck of pages. This is how a stage is built here, whatever its subject.
A topic skill (deep-interactive, vocational, deep-research,
teacher-style-clone, …) may shape what the stage contains — its structure, its
page types, how scenes are named — and where one is active its instructions win
on those questions. The sequence below is not one of those questions: it is the
same under every topic skill. Read this one first, then the topic skill.
Nothing here applies to a stage that already has pages. A stage with persisted
pages is edited, not built (see pro-editing).
The build sequence
Build a NEW stage only when there are no persisted pages yet. Then, in this order:
- Plan the stage in the conversation. Propose the page plan yourself —
each page with its
title,type(slide/quiz/interactive/pbl) andbrief(this page's teaching intent and content outline, the same information a planned outline slot used to carry) — in page order. Settle the plan with the user throughask_userbefore creating anything: there is no outline tool to plan with, so the plan is your words and their sign-off. A topic skill's structural constraints are a diagnostic the runtime checks against the real stage after each page; you decide how to act on it. create_stagewith the settled course title (pass the series folder'sfolderIdwhen the stage is part of a series, so it is filed in the same call). From here on, pass the returned stageId to every stage tool.set_roster, before any page is generated. Write the classroom the user settled: exactly one teacher, at least two agents in total, each with a concrete persona (2-3 sentences on personality and teaching/learning style, in the stage language) and a voice — calllist_voicesfirst and bind one of the returnedproviderId::voiceIdpairs, or the exact pairregister_voicereturned for a cloned voice; omit the binding when no usable voice exists. Every page's content and narration is written for the roster that exists when the page is generated, so a roster settled late is a roster half the stage never saw.generate_scenefor EACH settled page, in ascending order — one page per call, never more. Pass the page's settledtitle,typeandbrief(plusmaterialFactswhen the page's content comes from attached material); no planned outline is needed. Apblpage is generated the same way and lands as a full PBL project (projectV2) from its brief; a failed generation reports an error and writes nothing. Each call is the durable checkpoint for its page: the page survives an interruption only once the call has returned.list_scenesto verify every page you settled is actually persisted.
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 Changed · +19 lines 7275ef6f005e
- 8d ago First seen · 83 lines · 97 tokens per session scan A 8bf3fdbe5044
stage-design is a skill published in the GitHub repository THU-MAIC/OpenMAIC (33,238 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 1,324 once invoked, about $0.0005 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-30.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.
master-yinguang
A reference-based assistant for questions about Yinguang and Pure Land Buddhism, a Buddhist tradition focused on faith, ethical living, and practice connected with rebirth in the Pure Land. It can answer in Yinguang’s historical teaching style.