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 mycelium-cmbse/mycelium-hypha --skill metamodel-lookupgit clone --depth 1 https://github.com/mycelium-cmbse/mycelium-hyphaWrote 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/mycelium-cmbse/mycelium-hypha/metamodel-lookup)<a href="https://agentmods.dev/skills/mycelium-cmbse/mycelium-hypha/metamodel-lookup"><img src="https://agentmods.dev/badge/skills/mycelium-cmbse/mycelium-hypha/metamodel-lookup/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/mycelium-cmbse/mycelium-hypha/metamodel-lookup"><img src="https://agentmods.dev/badge/skills/mycelium-cmbse/mycelium-hypha/metamodel-lookup.svg" alt="Reviewed on agentmods" width="80" 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.02480 |
| Opus 5 | $0.00048 | $0.01240 |
| Sonnet 5 | $0.00019 | $0.00496 |
| Haiku 4.5 | $0.00010 | $0.00248 |
Grade A, and why
metamodel-lookup 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 12d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metamodel lookup
Answer questions about the structure of the KerML and SysML v2 metamodels using Hypha's generated knowledge base. Be exact and cite the source file.
Releases
The knowledge base is generated per upstream release tag (YYYY-MM, e.g. 2026-05), one folder
per release under knowledge/. Read knowledge/versions.json first: it lists the installed tags
newest first and names the default one to answer from.
jq -r '.default, (.versions[].tag)' knowledge/versions.json
Then substitute that tag for <tag> in every path below.
- Answer from the default release unless the user names one.
- Say which release you answered from — e.g. "in 2026-05,
PartUsage…". The metamodel changes between releases, so an unqualified structural claim is incomplete. - If the user asks about a release that is not installed, say so and list the ones that are, rather than answering from a different release silently.
- The tag is the version. Ignore the model URI inside the XMI (
…/SysML/20250201) — it tracks neither the release nor the content, and the same model can appear under several tags.
Knowledge base
KerML and SysML v2 are combined in one tree (the SysML v2 model is generated from the full
KerML + SysML metamodel, so KerML metaclasses such as Feature, Element and Membership live
here too):
knowledge/<tag>/metamodel/index.md— manifest: every metaclass grouped by package, plus## Enumeration typesand## Primitive typessections. Each entry links to its element file and carries a one-line summary.knowledge/<tag>/metamodel/elements/<Name>.md— one file per element. This includes metaclasses, enumerations (kind: enumeration) and primitive types (kind: primitive).knowledge/<tag>/metamodel/metamodel.json— the same metamodel as a structural graph, with the inheritance closures already computed. Use it for set-shaped and cross-cutting questions; see Querying the graph below.knowledge/<tag>/cross-references.json— links each element to the spec clauses that treat it, its BNF grammar production, and any worked example. See Cross-references.
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.
- 12d ago First seen · 180 lines · 97 tokens per session scan A fb1396e5ab8a
metamodel-lookup is a skill published in the GitHub repository mycelium-cmbse/mycelium-hypha (11 stars, last pushed 5d ago), licensed Apache-2.0. It adds 97 tokens to every session and 2,480 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-31.
Other skills, from other repositories
reqvire-ontology-authoring
Expert workflow for creating, extending, and validating Reqvire structural ontology elements for IT engineering, systems engineering, MBSE, and system-of-interest modeling. Use for competency-question-driven OWL/Turtle vocabulary, semantic-contract boundaries, ontology hierarchy, domain/range/property modeling…
reqvire-ontology-authoring
Expert workflow for creating, extending, and validating Reqvire structural ontology elements for IT engineering, systems engineering, MBSE, and system-of-interest modeling. Use for competency-question-driven OWL/Turtle vocabulary, semantic-contract boundaries, ontology hierarchy, domain/range/property modeling…
reqvire-concept-authoring
Expert workflow for authoring Reqvire native concept schemes and concepts as SKOS thesauri. Use when creating or revising concept-scheme or concept elements, designing controlled vocabularies, concept taxonomies, broader/narrower/related links, labels, definitions, scope notes, examples, mappings, concept scheme…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…