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/extra-org/extra/yaml-schemanpx skills add extra-org/extra --skill yaml-schemagit clone --depth 1 https://github.com/extra-org/extraWhat 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.00036 | $0.00511 |
| Opus 5 | $0.00018 | $0.00255 |
| Sonnet 5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
yaml-schema 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.
What it actually says
Skill: YAML Schema & Validation
When to use this skill
Use this when working on loading YAML configs, defining schema models, or
validating the Agent Engine specification. Primary task:
tasks/0002-yaml-schema-and-validation.md.
Files to read first
AGENTS.mddocs/YAML_SPEC.mdexamples/agents.ymlexamples/config.schema.jsondocs/adr/0002-yaml-is-compiled-not-executed-directly.md
Architecture rules
- YAML is declarative data, never code.
- The spec has two halves: flat declarations and
graphtopology. - Validation must happen before compilation.
- Runtime layers consume only validated/compiled models, never raw YAML dicts.
- Secrets are never values in YAML.
Implementation rules
- Define typed schema models in
src/agentplatform/spec. - Validation belongs in
src/agentplatform/validation. - Report all validation errors with useful locations.
- Enforce: required
systemandgraph; one graph root; graph ids exist inorchestratorsoragents; no cycles; referenced resolvers/tools/MCPs exist; orchestrators haveprompts.orchestrator; model overrides are complete; protected nodes require the access plugin at startup. - Keep schema/validation separate from the compiler.
Validation checklist
- Schema models cover
docs/YAML_SPEC.md. -
examples/agents.ymlvalidates successfully. - Dangling references, missing/multiple roots, and cycles fail clearly.
- Unknown keys and hardcoded secrets are rejected.
- Tests cover valid and invalid specs.
-
make checkpasses.
Common mistakes to avoid
- Mixing validation with compilation or runtime logic.
- Failing fast on the first error instead of collecting all errors.
- Reintroducing the old
definitions/hierarchyshape. - Letting unknown/typo'd keys pass silently.
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 · 64 lines · 36 tokens per session scan A 6e52ec1c86fb
yaml-schema is a skill published in the GitHub repository extra-org/extra (108 stars, last pushed 4d ago), licensed MIT. It adds 36 tokens to every session and 511 once invoked, about $0.0002 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-30.
Other skills, from other repositories
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
claude-to-deerflow
Interact with DeerFlow AI agent platform via its HTTP API. Use this skill when the user wants to send messages or questions to DeerFlow for research/analysis, start a DeerFlow conversation thread, check DeerFlow status or health, list available models/skills/agents in DeerFlow, manage DeerFlow memory, upload files to…
bootstrap
Generate a personalized SOUL.md through a warm, adaptive onboarding conversation. Trigger when the user wants to create, set up, or initialize their AI partner's identity — e.g., "create my SOUL.md", "bootstrap my agent", "set up my AI partner", "define who you are", "let's do onboarding", "personalize this AI", "make…
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
skill-reviewer
Reviews DeerFlow skill packages for readiness, triggers, safety boundaries, resources, and evidence. Invoke when users ask to audit, grade, or production-check an existing skill.
agent-reproduce-feature
Use when reproducing an existing Codex or Claude Code feature in Qwen Code or another agent CLI by choosing a reference agent, capturing HTTP request bodies, prompts, tool/function schemas, terminal output, and then implementing the matching behavior in the target repo.