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/regen-coordination/org-os-templatenpx agentmods add skills/regen-coordination/org-os-template/schema-generatorWrote 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/regen-coordination/org-os-template/schema-generator)<a href="https://agentmods.dev/skills/regen-coordination/org-os-template/schema-generator"><img src="https://agentmods.dev/badge/skills/regen-coordination/org-os-template/schema-generator/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/regen-coordination/org-os-template/schema-generator"><img src="https://agentmods.dev/badge/skills/regen-coordination/org-os-template/schema-generator.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.00015 | $0.00842 |
| Opus 5 | $0.00008 | $0.00421 |
| Sonnet 5 | $0.00003 | $0.00168 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
schema-generator 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schema Generator
What This Is
Regenerates the EIP-4824 compliant JSON-LD schemas in .well-known/ from the workspace's operational data (data/*.yaml) and package content (packages/operations/). Keeps machine-readable organizational identity current with actual data.
When to Use
- After updating
data/members.yaml(member changes) - After updating
data/projects.yaml(project changes) - After updating
data/finances.yaml(financial changes) - After adding new meeting notes
- On a schedule (daily or weekly)
- When
HEARTBEAT.mdhas a "regenerate schemas" task
When NOT to Use
- Just to check schema content (read
.well-known/*.jsondirectly) - If no data has changed
Usage
Run the generation script:
node scripts/generate-all-schemas.mjs
Or trigger via npm:
npm run generate:schemas
To validate after generation:
npm run validate:schemas
What Gets Generated
| Source | Generates | Location |
|---|---|---|
IDENTITY.md + federation.yaml |
dao.json |
.well-known/dao.json |
data/members.yaml |
members.json |
.well-known/members.json |
data/projects.yaml + project markdown |
projects.json |
.well-known/projects.json |
data/finances.yaml |
finances.json |
.well-known/finances.json |
packages/operations/meetings/*.md |
meetings.json |
.well-known/meetings.json |
Schema Verification
After generation, verify:
dao.jsonhas correctdaoURImatchingIDENTITY.mdmembers.jsonhas all active members fromdata/members.yamlprojects.jsonreflects current project statuses.well-known/is accessible at the deployed URL
HEARTBEAT Integration
After successful regeneration:
- Note in
memory/YYYY-MM-DD.md: "Schemas regenerated — [date]" - If automated, check GitHub Actions ran successfully
ReFi BCN Implementation Runbook (Operational)
When data changes (required sequence)
- Confirm changed sources:
data/*.yamlpackages/operations/meetings/packages/operations/projects/
- Run generation + validation:
npm run generate:schemas npm run validate:schemas - Verify critical parity:
.well-known/dao.jsonaligns withIDENTITY.md.well-known/members.jsonreflects current member scope.well-known/projects.jsonreflects latest project statuses
- Record run outcome in
memory/YYYY-MM-DD.md(success/failure + affected files) - If failure, open/refresh a blocker in
HEARTBEAT.mdwith exact error and owner.
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 · 108 lines · 15 tokens per session scan A a91aa3b425ca
schema-generator is a skill published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed 6d ago), licensed MIT. It adds 15 tokens to every session and 842 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
skypilot-multi-cloud-orchestration
Multi-cloud orchestration for ML workloads with automatic cost optimization. Use when you need to run training or batch jobs across multiple clouds, leverage spot instances with auto-recovery, or optimize GPU costs across providers.
modal-serverless-gpu
Serverless GPU cloud platform for running ML workloads. Use when you need on-demand GPU access without infrastructure management, deploying ML models as APIs, or running batch jobs with automatic scaling.
langchain-patterns
Use when langChain/LangGraph patterns — chains, agents, tools, memory, retrieval, graph workflows. Use when working with langchain patterns.
llamaindex-patterns
Use when llamaIndex data framework — ingestion, indexing, query engines, chat engines, agents. Use when working with llamaindex patterns.
model-fine-tuning
Use when fine-tune LLMs and ML models — LoRA, QLoRA, PEFT, Hugging Face. Dataset prep, training, evaluation, deployment. Use when working with model fine tuning.
ruvector
Use when generating and managing vector embeddings for semantic search and RAG retrieval across knowledge bases.