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 page-clonegit 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/page-clone)<a href="https://agentmods.dev/skills/thu-maic/openmaic/page-clone"><img src="https://agentmods.dev/badge/skills/thu-maic/openmaic/page-clone.svg" alt="Measured on agentmods" 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.00120 | $0.03121 |
| Opus 5 | $0.00060 | $0.01561 |
| Sonnet 5 | $0.00024 | $0.00624 |
| Haiku 4.5 | $0.00012 | $0.00312 |
Grade A, and why
page-clone 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 7d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloning one page's design
The design already exists on another page. Your job is to put new content into that design without redrawing it: copy the page, then swap what it says.
Copy-then-edit is the only clone path in this runtime. generate_scene always
re-rolls a page from its outline entry — the model invents a fresh element tree
every time — so calling it on a copied page destroys exactly the design you came
for. Nothing here validates the shape of your result either: the design is
preserved because you copied it, and the judgement about which elements are
content and which are the skeleton is yours.
The sequence
duplicate_scene({ templateSceneId, targetOrder, title })— an exact copy of the model page at the position you want (templateOrderworks too, but an id is safer). The copy carries the full content, no narration actions, and a new outline entry. Pass atitlethat names the NEW page; the entry inherits the model page's brief, and a copy still called 「第 3 章回顾」 misleads both the learner and the narration step.- Read the copy with
read_stage,path:/scenes/<order|id>,detail:"source"— this is your address space and your fidelity source. It returns the whole page's persisted JSON, including raw content HTML, inline spans, fonts, colours, fills, shadows, geometry and z-order, and it is the root your patch paths are written against: a field you read at/content/canvas/elements/2/contentis written back through that same path. Copy unchanged markup and style fields from this result; do not reconstruct them from stripped text. - Decide, element by element, what each one is. Content slots are the ones whose words belong to the old subject. Skeleton is everything else — rules, bands, page numbers, logos, decorative shapes, background art — and it stays untouched even when it holds text.
- Call
patch_stageonce per content slot, withop:"set"on the exact path that holds that slot's words —/content/canvas/elements/3/contentfor a paragraph,/content/canvas/elements/5/data/0/0/textfor a table cell. One leaf per call: everything you do not name keeps the value you copied.slide-dslis the manual for which field holds the words in each element type. Do not patch geometry or style paths while cloning — they ARE the design you copied. - Read the copy with
read_stage detail:"text"after the edits. It returns every text-bearing element as{ path, id, type, text }plus a page-widecombinedText, so you read the whole page's words in one call and get the pointer to fix with them. Search it for source-topic residue; the read reports, and you decide what is stale, thenset,remove, ordelete_elementit. generate_actionson the copy to give it narration (audio is on by default). A duplicated page arrives silent.
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.
- 7d ago First seen · 189 lines · 120 tokens per session scan A eeb220cf64b6
page-clone is a skill published in the GitHub repository THU-MAIC/OpenMAIC (32,028 stars, last pushed yesterday), licensed MIT. It adds 120 tokens to every session and 3,121 once invoked, about $0.0006 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
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…