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/reproducibility-auditWrote 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/reproducibility-audit)<a href="https://agentmods.dev/skills/docxology/template/reproducibility-audit"><img src="https://agentmods.dev/badge/skills/docxology/template/reproducibility-audit.svg" alt="Measured on agentmods" 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.00070 | $0.00694 |
| Opus 5 | $0.00035 | $0.00347 |
| Sonnet 5 | $0.00014 | $0.00139 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
template-reproducibility-audit 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 6d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reproducibility audit
Complements manuscript-claim-verification (claim truth) by focusing on stability of artifacts.
Natural invoke
- "Prove template_code_project is reproducible before Zenodo"
- "Numbers in the PDF don't match after a clean rebuild"
- "Double-run the pipeline and diff outputs"
Inputs to confirm
- Project — from
docs/_generated/active_projects.md.
Workflow
-
Determinism — fixed RNG seeds,
MPLBACKEND=Agg; no wall-clock/hostname/path leaks. List nondeterministic sources. -
Regenerate from clean — wipe working outputs, run core pipeline, regenerate manuscript variables. Capture exit status per stage.
-
Diff — compare regenerated
output/<name>/and manuscript variables vs prose assertions. Hand-typed numbers not from generated variables are findings even if equal. -
Double-run stability — regenerate twice with clean tree between; any run-1 vs run-2 diff is hard failure.
-
Fix — seed injection, variable-ize hard-typed numbers, remove timestamp leakage. Update
projects/<n>/AGENTS.mdand README.md with regeneration command. Never hand-editoutput/.
Deliverables
- Drift table: artifact | committed | regenerated | action.
- Commands + raw output; no invented coverage numbers.
Verification commands
uv sync
uv run python scripts/runner/execute_pipeline.py --project <project> --core-only
uv run python projects/<project>/scripts/z_generate_manuscript_variables.py
git stash --include-untracked -- output/<project> 2>/dev/null || true
uv run python scripts/runner/execute_pipeline.py --project <project> --core-only
git status --porcelain output/<project>
uv run python scripts/pipeline/stage_01_test.py --project <project>
uv run python -m infrastructure.validation.cli prerender projects/<project>/manuscript --repo-root .
uv run python -m infrastructure.validation.cli pdf output/<project>/pdf/
uv run python -m infrastructure.validation.cli integrity output/<project>/
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.
- 6d ago First seen · 72 lines · 70 tokens per session scan A 445b7c72d800
template-reproducibility-audit is a skill published in the GitHub repository docxology/template (19 stars, last pushed today), licensed Apache-2.0. It adds 70 tokens to every session and 694 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-08-30.
Other skills, from other repositories
symbolic-check
Use SymPy to prove or refute a self-authored algebraic identity, derivative, limit, comparative-static sign, or closed form. Use when exact symbolic manipulation can settle the claim. For parameter sweeps or full theorem proving, use $numerical-check or $lean-check.
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…
automotive-engineering-technician
Use when a task needs the judgment of an Automotive Engineering Technician — setting up and instrumenting test equipment (strain-gauge bridges, thermocouples, load/torque sensors) to an engineer's written test plan, selecting DAQ sample rate and an SAE J211 CFC filter class for a vehicle test channel, verifying…
calibration-technician
Use when a task needs the judgment of a Calibration Technologist/Technician — computing a Test Uncertainty Ratio (TUR) and deciding whether it meets the 4:1 target, building a measurement uncertainty budget (Type A/Type B, GUM-style) for a calibration, tracing a reference standard's chain of custody to NIST/SI…
agricultural-engineer
Use when a task needs the judgment of an agricultural engineer — sizing a center-pivot or drip irrigation system's peak capacity against crop water demand, computing lateral grain-bin wall pressure with Janssen's equation, sizing a waterway or tile-drainage system with Manning's equation and an NRCS design-storm…
agricultural-sciences-professor
Use when a task needs the judgment of a tenure-track or tenured Agricultural Sciences faculty member at a land-grant university — deciding whether to submit a grant this cycle versus wait, allocating time across the teaching/research/extension appointment split, diagnosing a stalled graduate student or field trial, or…