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.
git clone --depth 1 https://github.com/docxology/templatenpx agentmods add skills/docxology/template/documentationWrote 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/documentation)<a href="https://agentmods.dev/skills/docxology/template/documentation"><img src="https://agentmods.dev/badge/skills/docxology/template/documentation/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/documentation"><img src="https://agentmods.dev/badge/skills/docxology/template/documentation.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.00038 | $0.00598 |
| Opus 5.5 | $0.00015 | $0.00239 |
| Sonnet 5.5 | $0.00008 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
infrastructure-documentation 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 12d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Module
Figure metadata, file-bound publication registries, and source-derived documentation.
Generated figure registries (generated_figure_registry.py)
Use the fail-closed writer for deterministic project pipelines. Figure labels,
filenames, captions, and qualified generator names remain project-owned; the
shared writer verifies that every declared file exists before atomically
writing output/figures/figure_registry.json.
from infrastructure.documentation import publish_generated_figures
written = publish_generated_figures(
output_dir,
PROJECT_FIGURE_SPECS,
generated_paths,
schema_version="my-project-figure-registry-v1",
)
FigureManager (figure_manager.py)
Label-indexed metadata registration and persistence:
from infrastructure.documentation import FigureManager, FigureMetadata
manager = FigureManager()
# Register a figure (label auto-generated from filename if omitted)
manager.register_figure(
filename="results.png",
caption="Experimental results showing...",
label="fig:results",
section="Results",
)
# Get figure metadata by label
meta = manager.get_figure("fig:results") # Returns FigureMetadata | None
Manuscript figures
Author images and references in Pandoc form; pandoc-crossref assigns presentation numbers during rendering:
{#fig:results width=80%}
[@fig:results] summarizes the analysis.
Bind captions and alt text to the same analysis outputs as the figure. Use
publish_generated_figures or write_generated_figure_registry to validate actual
files before publication; metadata registration alone does not validate them.
Glossary & API Documentation (glossary_gen.py)
Generate API documentation and glossaries from source code:
from infrastructure.documentation import build_api_index, generate_markdown_table, ApiEntry
from infrastructure.documentation.glossary_gen import inject_between_markers
# Build API index from source
api_entries = build_api_index(source_dir)
# Generate markdown table
table = generate_markdown_table(api_entries)
# Inject between markers in a markdown file (operates on text, not a file path)
updated_text = inject_between_markers(
text=original_text,
begin_marker="<!-- API_START -->",
end_marker="<!-- API_END -->",
content=table,
)
What ships with it
25 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.
- __init__.py 1.1 KB runs code
- _coverage_snapshot_output.py 6.2 KB runs code
- _coverage_workspace.py 24 KB runs code
- _publication_records_check.py 7.6 KB runs code
- _publication_records_external.py 5.3 KB runs code
- _publication_records_load.py 6.8 KB runs code
- _publication_records_render.py 9.9 KB runs code
- _publication_records_types.py 6.5 KB runs code
- active_projects_doc.py 2.0 KB runs code
- AGENTS.md 7.2 KB
- api_reference_gen.py 22 KB runs code
- architecture_overview.py 15 KB runs code
- backlog_normalizer.py 14 KB runs code
- backlog.py 18 KB runs code
- counts_coverage.py 33 KB runs code
- counts_doc.py 25 KB runs code
- doc_module_refs.py 8.4 KB runs code
- figure_manager.py 7.8 KB runs code
- generate_glossary_cli.py 2.5 KB runs code
- generated_figure_registry.py 6.4 KB runs code
- glossary_gen.py 4.2 KB runs code
- publication_records.py 2.0 KB runs code
- publication_standalone.py 3.5 KB runs code
- README.md 7.9 KB
- stage_table.py 12 KB runs code
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.
- 12d ago Changed · -17 lines · -9 tokens per session 5d8a07552de6
- 1mo ago First seen · 112 lines · 47 tokens per session scan A 068c71292f7f
infrastructure-documentation is a skill published in the GitHub repository docxology/template (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 598 once invoked, about $0.0002 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
overleaf-latex-workflow
Working practices for LaTeX projects on Overleaf - finding the root file, compiling, reading the log, fixing errors, and keeping a shared paper buildable. Use when asked to write or revise a paper, fix a compile error, add figures, tables, sections or citations, or check that an Overleaf project still builds.
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.
consistency-polisher
A LaTeX layout helper that makes tables, figures, and captions follow consistent formatting throughout a research paper. LaTeX is a system often used to typeset academic documents.
float-optimizer
A document-layout helper for LaTeX, the system commonly used to typeset research papers. It adjusts how figures and tables are placed near the text that refers to them.
space-util-fixer
A LaTeX layout helper for improving how content fills pages and columns. It addresses issues such as isolated lines, large blank areas, incorrect page counts, and uneven columns in two-column papers.