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 manuscript-cross-referencesgit 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/manuscript-cross-references)<a href="https://agentmods.dev/skills/docxology/template/manuscript-cross-references"><img src="https://agentmods.dev/badge/skills/docxology/template/manuscript-cross-references.svg" alt="Measured on agentmods" 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.00087 | $0.00861 |
| Opus 5 | $0.00044 | $0.00430 |
| Sonnet 5 | $0.00017 | $0.00172 |
| Haiku 4.5 | $0.00009 | $0.00086 |
Grade A, and why
template-manuscript-cross-references 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 8d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manuscript cross-references (registry tokens)
For Pandoc-crossref @fig: / [@key] exemplars, see docs/guides/manuscript-semantics.md. This skill is for YAML registry + inline tokens.
Convention, not built-in infrastructure.
refs/labels.yamland[[FIG:]]/[[THMREF:]]/[[VAR:]]tokens are a project-authored convention, not a dedicated parser ininfrastructure/: no current public exemplar underprojects/templates/uses this style (all ship Pandoc-crossref), and there is nolabels.yaml-specific validator. Validation for a project that adopts this convention still runs through the genericinfrastructure.validation.cli markdown/prerenderchecks below plus project-local test coverage the project author writes — token expansion is the project's ownmanuscript_variables.py-style substitution, not a shared registry engine.
Natural invoke
- "Audit [[FIG:]] tokens in actinf_policy_entanglement_lean manuscript"
- "Hard-coded section numbers in prose — tokenize them"
- "labels.yaml has orphan keys"
Inputs to confirm
- Scope —
projects/<name>/manuscript/path or project name. - Style — confirm registry/token vs pure Pandoc-crossref (do not mix styles in repairs).
Workflow
-
Registry truth —
refs/labels.yaml(figures, equations, sections, theorems) andrefs/citations.yamlor hybridreferences.bib. Every token label must exist; every[@citekey]must resolve. -
No hard-coded numbers — prefer
[[THMREF:…]],[[SECREF:…]],[[FIGREF:…]],[[EQREF:…]]over "Theorem 7.3", "§8", "Figure 2" in body prose. -
Captions — YAML-stored captions may not expand
[[…]]unless renderer documents second pass. -
Sync — subsection headings and
labels.yamlsection/theorem numbers aligned; grep for stale numbers after renumbering. -
Bibliography — if
99_*uses[[CITELIST:all]], do not hand-maintain a parallel list. -
Report — missing/orphan/duplicate keys; hard-coded numbers to tokenize; concrete edits (file + snippet).
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.
- 8d ago First seen · 68 lines · 87 tokens per session scan A ef2dfd310bd4
template-manuscript-cross-references is a skill published in the GitHub repository docxology/template (19 stars, last pushed today), licensed Apache-2.0. It adds 87 tokens to every session and 861 once invoked, about $0.0004 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
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
aerospace-engineering-technician
Use when a task needs the judgment of an Aerospace Engineering and Operations Technologist/Technician — verifying an installed fastener's preload against a drawing's torque callout via the T=K·D·F relationship, reducing strain-gauge data from a structural proof-load test into stress and checking it against an…
aviation-inspector
Use when a task needs the judgment of an Aviation Inspector — determining whether an air carrier's fleet is in compliance with an Airworthiness Directive across a maintenance-records sample, deciding where the FAA's compliance-and-enforcement ladder places a finding (compliance action vs. Letter of Correction vs.…
compensation-benefits-specialist
Use when a task needs the judgment of a Compensation, Benefits, and Job Analysis Specialist — market-pricing a job against salary survey data, scoring a job through a point-factor or IPE job evaluation, running a pay-equity regression or cohort analysis, building or refreshing a salary structure and compa-ratio bands…
actor
Use when a task needs the judgment of a professional Actor — breaking down sides for a self-tape audition, preparing a character choice for rehearsal, deciding between two conflicting bookings, reading a contract offer for scale vs. scale-plus terms, or diagnosing why callbacks aren't converting to bookings.
advertising-promotions-manager
Use when a task needs the judgment of an Advertising and Promotions Manager — building a media plan backward from an objective and budget, briefing or evaluating creative against a brief, negotiating with agencies/media vendors, sanity-checking vendor-reported attribution, or reading a post-campaign debrief to…