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 runnergit 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/runner)<a href="https://agentmods.dev/skills/docxology/template/runner"><img src="https://agentmods.dev/badge/skills/docxology/template/runner/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/runner"><img src="https://agentmods.dev/badge/skills/docxology/template/runner.svg" alt="Reviewed on agentmods" width="80" 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.00042 | $0.00338 |
| Opus 5.5 | $0.00017 | $0.00135 |
| Sonnet 5.5 | $0.00008 | $0.00068 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
template-runner 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 2mo 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-runner
Pipeline execution runners in scripts/runner/.
When to use
Load this skill when you need to:
- Run the full pipeline for one or many projects
- Debug pipeline execution or PipelineExecutor
- Understand how
run.shdelegates to Python runners - Add or modify a runner script
Runner scripts
| Script | Delegates to |
|---|---|
execute_pipeline.py |
infrastructure.core.pipeline.PipelineExecutor |
execute_multi_project.py |
infrastructure.core.pipeline.PipelineExecutor (per project) |
run_matrix.py |
infrastructure.core.pipeline.run_matrix |
Bootstrap note
Runner scripts use parents[2] from scripts/runner/ — this reaches the
repo root (3 levels up: runner/ → scripts/ → repo root).
Pitfalls
execute_pipeline.pyre-exportsPipelineArgs,handle_hitl_command, etc. for test compatibility — do not remove__all__.run_matrix.pyreadsrun.configfor project selection; verify it exists.
What ships with it
12 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 445 B runs code
- AGENTS.md 2.6 KB
- archive_publication.py 5.7 KB runs code
- bundle_executable.py 1.5 KB runs code
- execute_multi_project.py 410 B runs code
- execute_pipeline.py 6.4 KB runs code
- exit_codes.py 3.0 KB runs code
- mcp_server_template.py 641 B runs code
- prepared_dispatch.py 7.8 KB runs code
- README.md 915 B
- repro_bundle.py 889 B runs code
- run_matrix.py 4.2 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.
- 2mo ago First seen · 46 lines · 42 tokens per session scan A 124154a81f56
template-runner is a skill published in the GitHub repository docxology/template (23 stars, last pushed today), licensed Apache-2.0. It adds 42 tokens to every session and 338 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-09-03.
Other skills, from other repositories
drug-design
End-to-end drug discovery pipeline orchestration. Deterministic Python script that auto-chains structure prediction, pocket detection, de novo design, docking, scoring, and ADMET filtering into reproducible workflows.
protein-design-workflow
End-to-end guidance for protein design pipelines. Use this skill when: (1) Starting a new protein design project, (2) Need step-by-step workflow guidance, (3) Understanding the full design pipeline, (4) Planning compute resources and timelines, (5) Integrating multiple design tools. For tool selection, use…
end-to-end-protein-design-workflow
End-to-end protein design pipeline guide across preparation, generation, validation, and filtering. Use this skill when: (1) Starting a new protein design project, (2) Need step-by-step workflow guidance, (3) Understanding the full design pipeline, (4) Planning compute resources and timelines, (5) Integrating multiple…
spatial-orchestrator
Route natural language requests and file inputs to registered SpatialClaw skills, and run named spatial analysis pipelines.
end-to-end-protein-design-workflow
End-to-end protein design pipeline guide across preparation, generation, validation, and filtering. Use this skill when: (1) Starting a new protein design project, (2) Need step-by-step workflow guidance, (3) Understanding the full design pipeline, (4) Planning compute resources and timelines, (5) Integrating multiple…
protein-design-workflow
End-to-end guidance for protein design pipelines. Use this skill when: (1) Starting a new protein design project, (2) Need step-by-step workflow guidance, (3) Understanding the full design pipeline, (4) Planning compute resources and timelines, (5) Integrating multiple design tools. For tool selection, use…