Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/metaschema-framework/claude-pluginsnpx agentmods add skills/metaschema-framework/claude-plugins/metaschema-module-authoringWrote 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/metaschema-framework/claude-plugins/metaschema-module-authoring)<a href="https://agentmods.dev/skills/metaschema-framework/claude-plugins/metaschema-module-authoring"><img src="https://agentmods.dev/badge/skills/metaschema-framework/claude-plugins/metaschema-module-authoring.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.00036 | $0.04537 |
| Opus 5 | $0.00018 | $0.02269 |
| Sonnet 5 | $0.00007 | $0.00907 |
| Haiku 4.5 | $0.00004 | $0.00454 |
Grade A, and why
metaschema-module-authoring 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 8d 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 — 673 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metaschema Module Authoring
This skill guides the creation and modification of Metaschema modules, which define information models that can be serialized to XML, JSON, or YAML.
Repository-specific conventions (file locations, namespaces, testing) are in .claude/rules/metaschema-authoring.md.
Module Authoring Formats
Metaschema modules can be authored in either XML or YAML format. These formats are semantically equivalent:
- Both produce identical module definitions
- Both enable parsing and serialization of data in all three formats (XML, JSON, YAML)
- The choice of authoring format does not limit the data formats the module can handle
For example, a module written in YAML can parse XML documents and serialize to JSON, and vice versa. The authoring format is purely a developer preference.
Module Structure
YAML Format
---
METASCHEMA:
schema-name: Human-readable module name
short-name: module-short-name
namespace: http://example.com/ns/module
json-base-uri: http://example.com/ns/module
schema-version: 1.0.0
definitions:
- object-type: assembly
name: root-assembly
# ... definition content
XML Format
<?xml version="1.0" encoding="UTF-8"?>
<METASCHEMA xmlns="http://csrc.nist.gov/ns/oscal/metaschema/1.0">
<schema-name>Human-readable module name</schema-name>
<schema-version>1.0.0</schema-version>
<short-name>module-short-name</short-name>
<namespace>http://example.com/ns/module</namespace>
<json-base-uri>http://example.com/ns/module</json-base-uri>
<define-assembly name="root-assembly">
<!-- definition content -->
</define-assembly>
</METASCHEMA>
Required Header Elements
| Element | Description |
|---|---|
schema-name |
Human-readable module name for documentation |
schema-version |
Semantic version (e.g., 1.0.0) |
short-name |
Unique identifier, used in artifact names |
namespace |
XML namespace URI for elements |
json-base-uri |
URI for JSON Schema $schema keyword |
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.
- 8d ago First seen · 673 lines · 36 tokens per session scan A 0ab6a02e370f
metaschema-module-authoring is a skill published in the GitHub repository metaschema-framework/claude-plugins (10 stars, last pushed 6mo ago), licensed CC0-1.0. It adds 36 tokens to every session and 4,537 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…