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 template-pitch-deckgit 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/template-pitch-deck)<a href="https://agentmods.dev/skills/docxology/template/template-pitch-deck"><img src="https://agentmods.dev/badge/skills/docxology/template/template-pitch-deck/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-pitch-deck"><img src="https://agentmods.dev/badge/skills/docxology/template/template-pitch-deck.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.00035 | $0.01279 |
| Opus 5.5 | $0.00014 | $0.00512 |
| Sonnet 5.5 | $0.00007 | $0.00256 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
template-pitch-deck 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
template-pitch-deck
Project-scoped skill for the in-repo exemplar at
projects/templates/template_pitch_deck/. Load this when working inside the project.
When to Use
- Working inside the
template_pitch_deckexemplar — running scripts, editing content, or regenerating outputs. - Forking this exemplar as the starting scaffold for a new pitch/grant-report/stakeholder-update deck.
- Adding a new format-agnostic slide renderer to
infrastructure/rendering/(e.g. this is the reference forDeckContent/Slide/DeckTheme). - Validating that the exemplar's contracts (thin-orchestrator, token honesty, cliché lint, diligence citation coverage, no-mocks testing) still hold after changes.
Quick Reference
# From the repository root
export PATH="$PWD/node_modules/.bin:$PATH"
uv run python projects/templates/template_pitch_deck/scripts/10_audit_deck_content.py
uv run python projects/templates/template_pitch_deck/scripts/15_generate_diagrams.py
uv run python projects/templates/template_pitch_deck/scripts/20_render_decks.py
uv run python projects/templates/template_pitch_deck/scripts/30_audit_diligence.py
uv run pytest projects/templates/template_pitch_deck/tests --cov=projects/templates/template_pitch_deck/src --cov-fail-under=90
uv run pytest tests/infra_tests/rendering/test_slide_deck.py tests/infra_tests/rendering/test_pptx_deck.py tests/infra_tests/rendering/test_mermaid_figure.py
PDF and PPTX are required project formats; the isolated project environment
installs python-pptx from this exemplar's own pyproject.toml. Mermaid
figures require the repository-pinned node_modules/.bin/mmdc on PATH.
Pitfalls
- Keep scripts thin. Content/validation logic belongs in this project's
src/; layout/drawing logic belongs ininfrastructure/rendering/{slide_deck,pptx_deck,mermaid_figure}.py— never inscripts/. - No mocks. All tests must use real YAML, real rendered files (read back with
pypdf/python-pptx), real repo introspection. - Every fact-bearing slide needs a
sourcecitation.src/diligence_audit.pyfails the build otherwise (title-kind slides are exempt). - Never hand-type a fact. All
PITCH_SUBJECT_*/EXEMPLAR_*token values come fromsrc/deck_tokens.py::build_deck_tokens, which reads them live from the repo — adding a new fact means adding a new live read, not a literal. - PDF/PPTX parity is load-bearing. The two renderers must always produce identical slide counts, text, fitted title sizes, and planned body line breaks for the same
DeckContent. The exact Helvetica fitter and content layout planner live inslide_deck.py;pptx_deck.pyconsumes their results rather than estimating again. A title below the legibility floor or body crossing the QR/footer protected band fails before either output is replaced. - Do not compress the public roster into other claims. Medium and long each dedicate one cited slide to all live exemplar names and a following, identically cited slide to the concrete-instance and uniform-contract claims. Tests bind each authored deck to its declared budget while proving the split, source, and exact live roster dynamically from
PUBLIC_PROJECT_NAMES. - Donut percentages require measured contrast. Keep outside labels theme-black on the white canvas, but choose theme-black or theme-white for each percentage from the real wedge artist's alpha-composited color. The project helper fails closed below 4.5:1, and tests inspect real Matplotlib artists rather than mocks.
- QR codes need a real
source_base_url.Slide.qr_url(drawn bottom-right, both renderers) is only populated whenmanuscript/config.yaml'sdeck.source_base_urlis non-empty —attach_qr_urlsis a no-op otherwise. New infra capabilities (QR generation reusesinfrastructure.steganography.barcode_generators.generate_qr_code) need their transitive dependency (qrcode[pil]) declared in THIS project's ownpyproject.toml, not just the root repo's — see the isolated-venv pitfall below. - Isolated-venv dependency check is not a one-time step. Every time new code imports a not-yet-used
infrastructure.*capability, re-runuv run python scripts/pipeline/stage_01_test.py --project templates/template_pitch_deck --project-only(not a bare root-venvpytest) — it is the only thing that catches a transitive dependency (reportlab/pypdf/Pillow/qrcode so far) missing from this project's ownpyproject.toml. - Outputs are disposable. Never hand-edit
output/; regenerate frommanuscript/+src/. This includesoutput/slides_standalone/*.md— generated per-slide pages, not hand-authored. - Run from the repo root. Commands assume the template monorepo root as working directory.
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 · 60 lines · 35 tokens per session scan A 5bfbad5ccc4a
template-pitch-deck is a skill published in the GitHub repository docxology/template (20 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 1,279 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
talisman
Generate a polished, on-brand PDF guide/handbook/whitepaper from a codebase or project using LaTeX (.tex -> .pdf) or Markdown->pandoc->pdf, with a designed cover page, the product's real brand colors and logo, a subtle branded page background, and TikZ diagrams (domain models, flows, state machines). Use for any…
latex-doc
Converts Markdown → LaTeX → PDF. Handles Mermaid diagrams, math, tables, citations, figures.
oma-pdf
Extract PDF text, headings, tables, and images into Markdown using opendataloader-pdf. Use for PDF parsing, not PDF layout creation.
liteparse
Parse local document files into LLM-ready content on the daemon itself — PDFs → Markdown / structured JSON (with bounding boxes) / page screenshots via the bundled lit CLI. PDF works out of the box, offline, zero external deps (Tesseract + PDFium are bundled): digital PDFs use a near-instant native text path…
slides
Create and edit presentation slide decks (.pptx) with PptxGenJS, bundled layout helpers, and render/validation utilities. Use when tasks involve building a new PowerPoint deck, recreating slides from screenshots/PDFs/reference decks, modifying slide content while preserving editable output, adding…
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…