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 validation-qualitygit 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/validation-quality)<a href="https://agentmods.dev/skills/docxology/template/validation-quality"><img src="https://agentmods.dev/badge/skills/docxology/template/validation-quality/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/validation-quality"><img src="https://agentmods.dev/badge/skills/docxology/template/validation-quality.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.00064 | $0.00626 |
| Opus 5.5 | $0.00026 | $0.00250 |
| Sonnet 5.5 | $0.00013 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
template-validation-quality 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 13d 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
Validation quality
Prefer actual CLI entrypoints in CLAUDE.md — not illustrative Python stubs.
Natural invoke
- "Validate markdown under projects/templates/template_prose_project/manuscript/"
- "PDF has unresolved references — run validation"
- "Strict prerender before render"
Inputs to confirm
- Target — manuscript dir, PDF path, or
output/<project>/. - Project — from active_projects when path ambiguous.
Workflow
-
Source markdown —
infrastructure.validation.cli markdownand/orprerender. -
Citations —
infrastructure.reference.citation validateon.bib. -
Links —
infrastructure.validation.cli links --repo-root . -
PDF — after render:
cli pdf output/<project>/pdf/ -
Integrity —
cli integrity output/<project>/ -
Report — diagnostic codes from validation; path + fix per issue.
Deliverables
- Command list with exit codes
- Issue table: code | file | message | fix
Verification commands
uv run python -m infrastructure.validation.cli prerender projects/<project>/manuscript --repo-root .
uv run python -m infrastructure.validation.cli markdown projects/<project>/manuscript --repo-root . --strict
uv run python -m infrastructure.reference.citation validate projects/<project>/manuscript/references.bib
uv run python -m infrastructure.validation.cli links --repo-root .
uv run python -m infrastructure.validation.cli pdf --project <project> --repo-root .
uv run python -m infrastructure.validation.cli integrity output/<project>/
uv run python -m infrastructure.prose.cli report projects/<project>/manuscript
When NOT to use
- Failing pipeline stage triage → pipeline-debugging
- Claim-by-claim manuscript audit → manuscript-claim-verification
References
What ships with it
2 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.
- 13d ago Changed f0a22dcc1241
- 1mo ago First seen · 78 lines · 64 tokens per session scan A 04821966bfed
template-validation-quality is a skill published in the GitHub repository docxology/template (20 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 626 once invoked, about $0.0003 per session on Opus 5.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
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…
taxonomy-vto
A reference guide for diagnosing visual problems in LaTeX research papers. It defines categories such as wasted page space, misplaced figures, inconsistent formatting, overflow, alignment, and template-migration issues.
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.
beamer-deck
Create an academic presentation as a LaTeX Beamer source and reviewed PDF with an original theme. Use when the requested deliverable is a conference, seminar, or lecture deck in Beamer. Not for PowerPoint or RevealJS; use $pptx or $quarto-deck.
latex-health-check
Compile all LaTeX projects and report cross-project build consistency. Use when checking whether a collection of papers builds cleanly. Not for rendered visual inspection after a clean build; use $latex-polish.
latex-polish
Inspect a cleanly compiling LaTeX document for source pathologies and rendered visual defects by linting and viewing selected PDF pages. Use when compilation succeeds but title pages, floats, tables, figures, or layout still need publication-quality review. Not for basic compilation health; use $latex-health-check.