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 docxology/template --skill metadatagit clone --depth 1 https://github.com/docxology/templateWrote 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/docxology/template/metadata)<a href="https://agentmods.dev/skills/docxology/template/metadata"><img src="https://agentmods.dev/badge/skills/docxology/template/metadata/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/docxology/template/metadata"><img src="https://agentmods.dev/badge/skills/docxology/template/metadata.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.00055 | $0.00387 |
| Opus 5 | $0.00028 | $0.00193 |
| Sonnet 5 | $0.00011 | $0.00077 |
| Haiku 4.5 | $0.00006 | $0.00039 |
Grade A, and why
infrastructure-metadata 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 today.
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
Metadata Module
Shared publication-metadata leaves consumed by the publishing, rendering,
documentation, and project layers. Extracted from infrastructure/publishing
so the rendering layer can import these surfaces without an inverted
dependency on the publishing package (RENDERING-LAYERING-1).
Repository URL normalization (repository_metadata.py)
from infrastructure.metadata.repository_metadata import normalized_repository_url
url = normalized_repository_url(publication) # explicit URL or owner/repo slug
Ebook metadata package (metadata_package.py)
from infrastructure.metadata.metadata_package import (
EbookPublicationMetadata,
ebook_metadata_from_config,
generate_epub_opf,
generate_metadata_json,
generate_metadata_package,
generate_onix_xml,
)
meta = ebook_metadata_from_config(config, project_slug)
paths = generate_metadata_package(meta, output_dir=Path("output/metadata"))
# paths == {"onix_xml": ..., "metadata_json": ..., "opf": ...} — the writer
# emits onix.xml, metadata.json, and package.opf itself; no manual write_text.
Invariants
- Leaf package: imports only stdlib plus
infrastructure.core; never imports publishing, rendering, or reporting. - Rendering may import this package directly; the layering guard
(
tests/infra_tests/rendering/test_layering.py) enforces zero rendering->publishing edges with an empty allowlist. - Historical paths
infrastructure.publishing.repository_metadataandinfrastructure.publishing.metadata_packageremain as re-export shims.
What ships with it
5 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.
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.
- today First seen · 48 lines · 55 tokens per session scan A 74afe2614059
infrastructure-metadata is a skill published in the GitHub repository docxology/template (19 stars, last pushed today), licensed Apache-2.0. It adds 55 tokens to every session and 387 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-09-09.
Other skills, from other repositories
talisman
Generate a polished, on-brand PDF guide/handbook/whitepaper from a codebase or project using LaTeX (.tex -> .pdf) or Markdown->pandoc->pdf, with a designed cover page, the product's real brand colors and logo, a subtle branded page background, and TikZ diagrams (domain models, flows, state machines). Use for any…
slides
Create and edit presentation slide decks (.pptx) with PptxGenJS, bundled layout helpers, and render/validation utilities. Use when tasks involve building a new PowerPoint deck, recreating slides from screenshots/PDFs/reference decks, modifying slide content while preserving editable output, adding…
paper-figures
Extract figures from downloaded papers and include them in survey/review reports. Use when the report covers other groups' work and benefits from their architecture diagrams, experimental plots, or system schematics. Your brain prompt supplies the absolute path to the extract-figures script as {{EXTRACTFIGURES}} — use…
liteparse
Parse documents into LLM-ready content entirely on the local machine — PDF / DOCX / XLSX / PPTX / images → Markdown, structured JSON (with bounding boxes), or page screenshots, via the lit CLI. No cloud, no LLM, works offline. Use whenever the user attaches or points to a document that must be read before reasoning…
overleaf
Sync and manage Overleaf LaTeX projects from the command line. Pull projects locally, push changes back, compile PDFs, and download compile outputs like .bbl files for arXiv submissions. Use when working with LaTeX, Overleaf, academic papers, or arXiv.
bib-parse
Extract citations from a PDF and generate a validated .bib file. Use when the user asks to extract citations from a PDF and generate a validated .bib file. Reads the PDF, identifies referenced works, constructs BibTeX entries, and verifies metadata.