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 gracefullight/docusaurus-plugins --skill oma-skill-creatorgit clone --depth 1 https://github.com/gracefullight/docusaurus-pluginsWrote 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/gracefullight/docusaurus-plugins/oma-skill-creator)<a href="https://agentmods.dev/skills/gracefullight/docusaurus-plugins/oma-skill-creator"><img src="https://agentmods.dev/badge/skills/gracefullight/docusaurus-plugins/oma-skill-creator/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/skills/gracefullight/docusaurus-plugins/oma-skill-creator"><img src="https://agentmods.dev/badge/skills/gracefullight/docusaurus-plugins/oma-skill-creator.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.00072 | $0.02199 |
| Opus 5.5 | $0.00029 | $0.00880 |
| Sonnet 5.5 | $0.00014 | $0.00440 |
| Haiku 4.5 | $0.00007 | $0.00220 |
Grade A, and why
oma-skill-creator 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 1mo 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.
This is a copy
91% identical to oma-skill-creator — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator - SSL-lite Skill Authoring Specialist
Scheduling
Goal
Create, revise, and validate OMA skills using the SSL-lite Markdown structure derived from Scheduling-Structural-Logical skill representation while keeping the result readable, executable, and maintainable.
Intent signature
- User asks to create a new OMA skill, agent skill, specialist skill, or
.agents/skills/*/SKILL.md. - User asks to convert or normalize a skill into the project skill format.
- User asks whether a skill has enough scheduling, structural, logical, reference, or canonical execution detail.
- User mentions SSL-lite, Scheduling / Structural / Logical, skill format, skill template, or skill creator.
When to use
- Creating a new skill under
.agents/skills/{name}/SKILL.md - Updating an existing OMA skill to the SSL-lite format
- Adding
Canonical command pathorCanonical workflow pathto an execution-heavy skill - Auditing whether a skill is usable by routing, execution, validation, and recovery logic
- Deciding whether detailed examples belong inline or in
resources/
When NOT to use
- Installing third-party skills into
$CODEX_HOME/skills-> use Codex's built-in skill installer (external; not an OMA skill) - Creating a Codex plugin bundle -> use Codex's plugin tooling (external; not an OMA skill)
- Writing a general project plan unrelated to skill authoring -> use PM Agent
- Editing product code, infrastructure, frontend, backend, or mobile implementation directly -> use the matching specialist skill
Expected inputs
skill_name: target directory name, preferablyoma-{domain}skill_goal: capability the skill should addtrigger_intents: user prompts or domains that should activate the skillboundaries: when the skill should not be used and which skill should handle those casesexecution_model: whether the skill is command-heavy, workflow-heavy, judgment-heavy, or reference-heavy- Existing files, tools, commands, resources, or standards the skill must preserve
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 165 lines · 72 tokens per session scan A 0d6e68855867
oma-skill-creator is a skill published in the GitHub repository gracefullight/docusaurus-plugins (23 stars, last pushed 27d ago), licensed MIT. It adds 72 tokens to every session and 2,199 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to oma-skill-creator, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
claude-code-dmwork
Connect to DMWork messaging platform as an AI bot via the OpenClaw DMWork adapter plugin.
vs-chat
Conversational search runtime: send messages, keep sessions consistent, and verify retrieval behavior and responses.
cometchat-android-v6-core
Foundational rules for the CometChat Android UI Kit v6 — the two UI cohorts and their artifacts, credentials via the gitignored assets settings file, initFromSettings → login → render ordering, the component map, and the production-ready core chat surface. Read this first for any Android CometChat task. Triggers…
cometchat-react-v7-core
Add CometChat chat to a React app end-to-end — detect the project, get & verify dashboard credentials, init→login→render with CometChatProvider, and the drop-in conversation UI. The core knowledge every other React v7 skill builds on. Triggers: 'add chat to my react app', 'integrate cometchat react', 'set up cometchat…
cometchat-android-v6-compose-placement
Where the CometChat Android v6 chat UI goes in a Jetpack Compose app — the default conversations→message NavHost flow, growing to the tab-based app (chats/users/groups/calls + detail, thread and search routes + incoming calls), a single one-to-one screen, or chat embedded in an existing composable, with a correct back…
cometchat-android-v5-sdk
Build chat on Android with the headless CometChat Chat SDK v5 and your OWN UI — init/login ordering, the method map, request-builder pagination, listener lifecycle, and a production-ready app surface (optimistic updates, error states, sized shell). Use when the app needs custom UI instead of the drop-in UI Kit.…