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 skills add dandye/ai-runbooks --skill design-metadata-schemagit clone --depth 1 https://github.com/dandye/ai-runbooksWrote 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/dandye/ai-runbooks/design-metadata-schema)<a href="https://agentmods.dev/skills/dandye/ai-runbooks/design-metadata-schema"><img src="https://agentmods.dev/badge/skills/dandye/ai-runbooks/design-metadata-schema/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/dandye/ai-runbooks/design-metadata-schema"><img src="https://agentmods.dev/badge/skills/dandye/ai-runbooks/design-metadata-schema.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.00539 |
| Opus 5 | $0.00010 | $0.00269 |
| Sonnet 5 | $0.00004 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
design-metadata-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 11d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Metadata Schema Skill
Develop a comprehensive metadata schema for content management. This skill defines structured fields, validation rules, and standards compliance to improve searchability and management.
Inputs
PATH- The content domain to apply the schema to (e.g., "/content")OUTPUT_FORMAT- (Optional) The output format for the schema, e.g., "json-schema", "xml", "markdown" (default: "json-schema")DUBLIN_CORE- (Optional) Boolean, whether to align with Dublin Core standards (default: true)CUSTOM_FIELDS- (Optional) List of custom business-specific fields to includeVALIDATION_RULES- (Optional) Boolean, whether to define validation logic for fields (default: true)
Workflow
Step 1: Requirement Analysis
Analyze the content types at PATH to determine metadata needs.
- Identify common attributes (Title, Date, Author).
- Identify specific attributes (Product ID, Version, Region).
Step 2: Schema Definition
Define the fields and their properties.
- Standard Fields: Map to Dublin Core (Title, Creator, Subject, etc.) if enabled.
- Custom Fields: Define fields specified in
CUSTOM_FIELDSor discovered during analysis.
Step 3: Constraints & Validation
If VALIDATION_RULES is true, define:
- Data Types: String, Date, Integer, Boolean, Enum.
- Required/Optional: Cardinality constraints.
- Controlled Vocabularies: Allowed values for specific fields.
Step 4: Schema Output
Generate the schema definition in the requested OUTPUT_FORMAT (e.g., JSON Schema, XML Schema, or Markdown Table).
Required Outputs
A METADATA_SCHEMA object in the specified OUTPUT_FORMAT containing:
- Field Dictionary: Name, Description, Type, Multiplicity.
- Validation Logic: Rules for data entry.
- Mapping: Correspondence to standards (like Dublin Core).
Quick Reference
- Purpose: Standardize content tagging for consistency and interoperability.
- Standards: Dublin Core, Schema.org.
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.
- 11d ago First seen · 61 lines · 19 tokens per session scan A 51a8febef5f3
design-metadata-schema is a skill published in the GitHub repository dandye/ai-runbooks (124 stars, last pushed 27d ago), licensed Apache-2.0. It adds 19 tokens to every session and 539 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-08-30.
Other skills, from other repositories
baoyu-youtube-transcript
A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
overleaf-sync
A two-way connection between a local paper folder and Overleaf, a web-based LaTeX editor for writing research papers. It lets you move changes between the local files and the shared Overleaf project.