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 agentmods add skills/volantlabs/vellis/sysml-referencenpx skills add volantlabs/vellis --skill sysml-referencegit clone --depth 1 https://github.com/volantlabs/vellisWhat 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 | $0.00092 | $0.00799 |
| Opus 5 | $0.00046 | $0.00400 |
| Sonnet 5 | $0.00018 | $0.00160 |
| Haiku 4.5 | $0.00009 | $0.00080 |
Grade A, and why
sysml-reference 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 2d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SysML Reference
Use the committed page corpus as a searchable projection of the pinned official PDFs. Treat the PDFs as authoritative and the Markdown as generated retrieval material.
Workflow
-
Unless the request already supplies an exact specification section or page, the first corpus command must be the ranked, outline-aware finder. Pass the modeling question or a concise description, not just one generic word:
just model-reference-find "<question or construct description>"Do not replace this first step with a broad
rgoverpages/. The finder is designed to handle natural wording without loading every textual match. -
Review the ranked section titles and snippets. Open the best page, then read only the adjacent pages needed to finish the section. The finder routes to evidence; its rank is not an answer. If one specification is clearly in scope, rerun with
--specification sysml-2.0or--specification kerml-1.0before broadening the search. -
If results are broad or use different terminology, search outline headings before raw page text:
rg -n -i '<construct or section phrase>' reference/specifications/{sysml-2.0,kerml-1.0}/index.mdUse raw
rgoverpages/only for exact phrases, identifiers, or a cited section number. -
Follow normative cross-references between SysML and KerML. Search by both the construct name and any referenced section number, and prefer the normative Clause 8 definition when Clause 7 is explicitly informative.
-
Inspect the pinned PDF under
.cache/sysml/formal/when a table, figure, mathematical layout, indentation, or questionable extraction affects the conclusion. Runjust model-setupif it is absent. -
Separate the result into:
- normative SysML or KerML semantics supported by cited sections and pages;
- informative examples in the specifications;
- Vellis repository profile or modeling conventions;
- explicit inference where the sources do not directly decide the question.
-
State the reference basis for every consequential conclusion using specification, section, and printed or physical page. Never present training-memory recall as specification evidence.
-
After changing a model, run the narrow scoped check while editing and the official validation gate required by the repository before completion.
What ships with it
1 file 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.
- 2d ago First seen · 65 lines · 92 tokens per session scan A afd9477f04a5
sysml-reference is a skill published in the GitHub repository volantlabs/vellis (8 stars, last pushed 9d ago), licensed Apache-2.0. It adds 92 tokens to every session and 799 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
ori-memory
Persistent agent memory with learning retrieval. Knowledge graph on markdown files — capture insights, decisions, research, and learnings during work, then retrieve them weeks or months later. Use when knowledge is too valuable to lose but too much to inject into every prompt.
svoboda-profiler
Use when asked to profile someone, unpack a person, build a psychological portrait, run a Svoboda session, or map life state. Triggers on распаковка, профилирование, психопортрет, точка А, колесо баланса, profile someone, unpack, svoboda session.
vault-scaffolder
Use when a completed svoboda profile.yaml exists and a new Personal OS needs to be personalized in the current workspace.
lint
Use weekly or after major ingest sessions to check wiki health.
start
One-word self-unfolding onboarding. Sets up a fresh, unpersonalized vault end-to-end — installs the memory engine, runs the profile interview, scaffolds the vault, and teaches the user as it goes. The single front door.
pos-audit
Use when checking overall Personal OS health or diagnosing system gaps.