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/template-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/template-template)<a href="https://agentmods.dev/skills/docxology/template/template-template"><img src="https://agentmods.dev/badge/skills/docxology/template/template-template/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/template-template"><img src="https://agentmods.dev/badge/skills/docxology/template/template-template.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.00032 | $0.00457 |
| Opus 5.5 | $0.00013 | $0.00183 |
| Sonnet 5.5 | $0.00006 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
template-template 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 1mo 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
template-template
Project-scoped skill for the in-repo exemplar at
projects/templates/template_template/. Load this when working inside the project.
When to Use
- Working inside the
template_templateexemplar — running scripts, editing source, or regenerating outputs. - Forking this exemplar as the starting scaffold for a new research project.
- Validating that the exemplar's contracts (thin-orchestrator, layer boundaries, no-mocks testing) still hold after changes.
Quick Reference
# From the repository root
uv run pytest projects/templates/template_template/tests --cov=projects/templates/template_template/src --cov-fail-under=90
uv run python scripts/pipeline/stage_02_analysis.py --project templates/template_template
uv run python scripts/pipeline/stage_03_render.py --project templates/template_template
uv run python scripts/pipeline/stage_04_validate.py --project templates/template_template
uv run python scripts/pipeline/stage_05_copy.py --project templates/template_template
Pitfalls
- Keep scripts thin. Business logic belongs in
src/or sharedinfrastructure/, not inscripts/. - No mocks. All tests must use real data, real files, and real computation.
- Outputs are disposable. Never hand-edit
output/— regenerate from source and config. - Run from the repo root. Commands assume the template monorepo root
as working directory unless the child
AGENTS.mdstates otherwise.
Cross-refs
- Project contract:
AGENTS.md - README:
README.md - TODO:
TODO.md - Exemplar roster:
projects/AGENTS.md
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.
- 1mo ago First seen · 51 lines · 32 tokens per session scan A 673e05f1e3fc
template-template is a skill published in the GitHub repository docxology/template (20 stars, last pushed 2d ago), licensed Apache-2.0. It adds 32 tokens to every session and 457 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
ledger-tasks-yylo
Durable in-repo task state for coding agents — Kanban tasks with stable IDs, evidence-backed status marks, blocked-by dependencies, and next-ready selection. Use when starting, selecting, sequencing, or closing implementation tasks for a coding-agent project.
construction-trades-supervisor
Use when a task needs the judgment of a Construction Trades Supervisor (foreman) — allocating a crew's daily task assignments against a labor-unit budget, deciding whether today's scope requires a formally designated OSHA competent person, arbitrating a trade-sequencing conflict between crews needing the same physical…
architectural-engineering-manager
Use when a task needs the judgment of an Architecture/Engineering firm or department manager — pricing a project fee (lump sum vs. hourly vs. % of construction cost), staffing a project against backlog, evaluating scope creep on a fixed-fee job, managing professional liability exposure, or deciding whether to pursue a…
biomass-power-plant-manager
Use when a task needs the judgment of a Biomass Power Plant Manager — running a biomass-fired power generation facility, managing fuel supply logistics and quality variability, evaluating combustion/efficiency problems, or balancing generation output against fuel cost and emissions constraints.
chief-executive
Use when a task needs the judgment of a CEO/chief executive — setting company strategy, allocating scarce resources (capital, headcount, attention) across competing priorities, making a call that only the top of the org can make, or communicating direction to the board, investors, or the whole company.
clinical-research-coordinator
Use when a task needs the judgment of a Clinical Research Coordinator — managing patient recruitment/enrollment against a trial's screen-fail rate, handling a protocol deviation, tracking informed consent and regulatory documentation, or coordinating a multi-visit study schedule against patient retention risk.