vellis: Skill for Codex

.agents/skills/rtg-schema-design/SKILL.md

rtg-schema-design is a skill for Codex from volantlabs/vellis. It costs 68 tokens per session (415 once invoked), scanned A, original, Apache-2.0.

A guide for designing RTG knowledge-graph schemas: structured descriptions of things, their facts, and their relationships. It helps turn real-world requirements into a language-independent data model.

In plain words
What is it for?
Use it to choose entities, properties, relationship types, required fields, compatibility rules, and safe migration boundaries for an RTG graph.
Why use it?
It reduces ambiguity before a graph schema is created or changed. It also helps preserve incomplete information and avoid changes that break existing data or queries.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is volantlabs/vellis's own configuration. It tells Codex how to work on vellis itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vellis configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/volantlabs/vellis/main/.agents/skills/rtg-schema-design/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/volantlabs/vellis

Made for: Codex.

Wrote 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.

agentmods badge for rtg-schema-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/volantlabs/vellis/rtg-schema-design/github.svg)](https://agentmods.dev/skills/volantlabs/vellis/rtg-schema-design)
Your own site
<a href="https://agentmods.dev/skills/volantlabs/vellis/rtg-schema-design"><img src="https://agentmods.dev/badge/skills/volantlabs/vellis/rtg-schema-design/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.

agentmods 80×15 button for rtg-schema-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/volantlabs/vellis/rtg-schema-design"><img src="https://agentmods.dev/badge/skills/volantlabs/vellis/rtg-schema-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 415 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00068 $0.00415
Opus 5 $0.00034 $0.00208
Sonnet 5 $0.00014 $0.00083
Haiku 4.5 $0.00007 $0.00042

Measured 9d ago against content hash 4a2c08a98265, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

rtg-schema-design 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 9d 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.

.agents/skills/rtg-schema-design/SKILL.md · 43 lines

What it actually says

RTG Schema Design

Turn domain meaning into the smallest precise RTG schema that supports identity, typed facts, relationships, queries, and safe evolution. Preserve partial knowledge and implementation freedom.

Read schema-design.md before authoring or approving a schema.

Workflow

  1. Elicit the questions, decisions, and ordinary requests the graph must support.
  2. Inspect the existing schema and representative live data when evolving a graph.
  3. Identify independently addressable things as anchors, coherent typed facts as associated data, and meaningful navigable relationships as links.
  4. Define stable type keys, property kinds, required fields, deliberate field refinements, and allowed link endpoints.
  5. Walk through incomplete, duplicate, evolving, and query scenarios. Remove requirements that would force agents to invent facts.
  6. Explain the proposed semantics and compatibility impact. Obtain human approval before a consequential live-schema change.
  7. Stage and validate the migration, inspect findings, cut over atomically, then validate live data and representative queries.

Output Standard

Produce a reviewable schema proposal containing:

  • the user outcomes and queries it supports;
  • anchor, associated-data, and link definitions with rationale;
  • exact property kinds, optionality, justified refinements, and link endpoint sets;
  • identity, naming, and duplicate-handling rules;
  • compatibility and migration effects on existing data;
  • validation and acceptance scenarios;
  • intentional freedoms and deferred specializations.

Stop when the schema is sufficient for correct storage, linking, querying, extension, and black-box validation. Do not model agent prompts, private implementation structure, or speculative domain detail as schema.

Files

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.

Changes

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.

  1. 9d ago First seen · 43 lines · 68 tokens per session scan A 4a2c08a98265

Subscribe to this mod's changes

rtg-schema-design is a skill published in the GitHub repository volantlabs/vellis (8 stars, last pushed today), licensed Apache-2.0. It adds 68 tokens to every session and 415 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

omnigraph

Operate OmniGraph graphs and deployments. Use for .pg schemas, .gq queries, OmniGraph CLI commands, file:///s3:///az:// graph URIs, cluster.yaml, operator config, bearer-authenticated servers, graph-backed knowledge or memory, Blob values, embeddings, branches, commits, and change feeds. Apply especially before schema…

ModernRelay/omnigraph · 94 tokens

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.

aayoawoyemi/Ori-Mnemos · 54 tokens

binder-modeling

Binder data modeling — define entity types, fields, relations, constraints, views, and navigation. Use when asked to "create a type", "add a field", "define a schema", "set up relations", "model entities", "create a view", "set up navigation", "render entities as files", or design a binder workspace schema.

mpazik/Binder · 74 tokens

binder-cli

Binder CLI for knowledge graph operations — CRUD, search, schema inspection, transaction import, docs rendering. Use when asked to "query binder", "search records", "create a record", "check the schema", "import transactions", "undo changes", or work with a binder workspace.

mpazik/Binder · 60 tokens

binder-import

Import external data into a Binder workspace. Handles CSV, JSON, YAML, Markdown files, and directories of Markdown. Use when asked to "import data", "load records from a file", "ingest documents", "migrate data into binder", or bulk-create records from an external source.

mpazik/Binder · 62 tokens

claude-memory

Access the persistent memory database (PostgreSQL claudememory) for long-term context across Claude Code sessions. Triggers on "what do I know about", "memory lookup", "recall", "memory db", "what did we decide about", "similar conversations", "lookup context", "/memory". Provides semantic search, SQL queries and the…

mkupermann/throughline · 81 tokens