schema-generator

schema-generator is a skill for Claude Code, Codex from regen-coordination/org-os-template. It costs 15 tokens per session (842 once invoked), scanned A, original, MIT.

A generator that rebuilds machine-readable EIP-4824 organizational schemas from workspace data and package content. These schemas describe organizational identity, members, projects, and related information in a format computers can read.

In plain words
What is it for?
Use it after changing member, project, finance, or meeting data, and then validate the generated files.
Why use it?
It keeps published schema files aligned with the latest operational data instead of requiring manual updates.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: built for openclaw.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/generate-all-schemas.mjs.

Good fit Use it after changing member, project, finance, or meeting data, and then validate the generated files.

Compare 6 skills from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/regen-coordination/org-os-template
agentmods
npx agentmods add skills/regen-coordination/org-os-template/schema-generator

Made for: Claude Code, 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 schema-generator

README.md
[![agentmods](https://agentmods.dev/badge/skills/regen-coordination/org-os-template/schema-generator/github.svg)](https://agentmods.dev/skills/regen-coordination/org-os-template/schema-generator)
Your own site
<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.

agentmods 80×15 button for schema-generator

Your own site · 80×15
<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>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 842 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.00015 $0.00842
Opus 5 $0.00008 $0.00421
Sonnet 5 $0.00003 $0.00168
Haiku 4.5 $0.00002 $0.00084

Measured 8d ago against content hash a91aa3b425ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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.

skills/schema-generator/SKILL.md · 108 lines

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.md has a "regenerate schemas" task

When NOT to Use

  • Just to check schema content (read .well-known/*.json directly)
  • 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:

  1. dao.json has correct daoURI matching IDENTITY.md
  2. members.json has all active members from data/members.yaml
  3. projects.json reflects current project statuses
  4. .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)

  1. Confirm changed sources:
    • data/*.yaml
    • packages/operations/meetings/
    • packages/operations/projects/
  2. Run generation + validation:
    npm run generate:schemas
    npm run validate:schemas
    
  3. Verify critical parity:
    • .well-known/dao.json aligns with IDENTITY.md
    • .well-known/members.json reflects current member scope
    • .well-known/projects.json reflects latest project statuses
  4. Record run outcome in memory/YYYY-MM-DD.md (success/failure + affected files)
  5. If failure, open/refresh a blocker in HEARTBEAT.md with exact error and owner.

Read the full file on GitHub · 108 lines

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. 8d ago First seen · 108 lines · 15 tokens per session scan A a91aa3b425ca

Subscribe to this mod's changes

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.