Borrowing it
Nothing to install: this file belongs to volantlabs/vellis. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/volantlabs/vellis/main/.agents/skills/component-authoring/SKILL.mdgit clone --depth 1 https://github.com/volantlabs/vellisWrote 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/volantlabs/vellis/component-authoring)<a href="https://agentmods.dev/skills/volantlabs/vellis/component-authoring"><img src="https://agentmods.dev/badge/skills/volantlabs/vellis/component-authoring/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/volantlabs/vellis/component-authoring"><img src="https://agentmods.dev/badge/skills/volantlabs/vellis/component-authoring.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.00071 | $0.01935 |
| Opus 5.5 | $0.00028 | $0.00774 |
| Sonnet 5.5 | $0.00014 | $0.00387 |
| Haiku 4.5 | $0.00007 | $0.00194 |
Grade A, and why
component-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 2mo 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Authoring
Author the durable component and application design in textual SysML v2 under model/. Treat
generated Markdown as a view, never as an independent contract.
Goal
Model enough contract-significant structure and behavior that a human or agent can:
- understand what the component owns and exposes;
- invoke and compose its public contracts;
- reason about abstract state changes and invariant preservation;
- substitute another conforming realization;
- derive black-box verification scenarios.
Leave private helpers, algorithms, implementation data structures, performance strategy, and language-specific type hierarchies to realizations.
Conformance Hierarchy
Treat every chosen abstraction boundary as an engineered black box. A component realization conforms when its public structure, behavior, abstract state effects, failures, invariants, and verification obligations match the model, regardless of implementation language or internal design. A composed subsystem or application is another modeled black box: its internal roles must conform to their component contracts, and its own external actions, behavior, state, invariants, and use cases must conform at the higher boundary.
Model downward into algorithms, deployment, hardware, or implementation structure only when that layer is itself an intentional engineering subject or affects an observable contract. Do not make implementation fidelity the default completeness criterion.
Required Resources
- Use the
sysml-referenceskill before making or reviewing a SysML/KerML syntax or semantics decision. Cite the relevant specification section and page for consequential choices. - Read
references/component-modeling-pattern.mdbefore authoring or materially revising a model. - Read
references/behavior-detail.mdwhen deciding how much behavior to formalize. - Read
references/model-organization.mdwhen creating or changing a model library, package boundary, shared vocabulary, application/library dependency, or runtime realization. - Read
references/application-composition.mdfor application, controller, adapter, or use-case work. - Read
references/boundary-quality.mdwhen reviewing ownership or considering a split or merge. - Read
references/examples.mdwhen a representative storage, query, or controller pattern helps.
What ships with it
7 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.
- 2mo ago First seen · 168 lines · 71 tokens per session scan A 3196579bf89e
component-authoring is a skill published in the GitHub repository volantlabs/vellis (9 stars, last pushed 4d ago), licensed Apache-2.0. It adds 71 tokens to every session and 1,935 once invoked, about $0.0003 per session on Opus 5.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
dkg-importer
Bulk-import a large RDF graph (code graph, corpus, GitHub history, etc.) into a DKG node's working memory. Use this skill when you need to push more than a few thousand triples in a single import — it codifies the chunking budgets, the assertion-loop shape, the resumability manifest, and the canonical URI rules so…
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.
dkg-node
The DKG V10 Node is your primary memory system. This skill teaches you to operate your node's three-layer verifiable memory — write and retrieve private drafts in Working Memory, share with peers in Shared Working Memory, and publish permanently to Verifiable Memory on-chain.
example-skill
Example module showing the format. Use when: testing /enable-modules, learning to author a module.
graph-ask
Ask any natural language question about the memory graph. You generate Cypher directly and execute it. Use when the user has a complex or ad-hoc question that the standard graph tools don't cover.
capture-knowledge
A guide for saving useful, reusable knowledge from conversations and documents into a structured personal knowledge base. It separates original source material from concise pages about individual concepts.