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-siaWrote 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-sia)<a href="https://agentmods.dev/skills/docxology/template/template-sia"><img src="https://agentmods.dev/badge/skills/docxology/template/template-sia.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.00035 | $0.00494 |
| Opus 5 | $0.00017 | $0.00247 |
| Sonnet 5 | $0.00007 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
template-sia 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 4d 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-sia
Project-scoped skill for the in-repo exemplar at
projects/templates/template_sia/. Load this when working inside the project.
When to Use
- Working inside the
template_siaexemplar — 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_sia/tests --cov=projects/templates/template_sia/src --cov-fail-under=90
uv run python scripts/pipeline/stage_02_analysis.py --project templates/template_sia
uv run python scripts/pipeline/stage_03_render.py --project templates/template_sia
uv run python scripts/pipeline/stage_04_validate.py --project templates/template_sia
uv run python scripts/pipeline/stage_05_copy.py --project templates/template_sia
Pitfalls
- Keep scripts thin. Business logic belongs in
src/or sharedinfrastructure/, not inscripts/.src/loop.pyowns the project adapter;scripts/run_sia_loop.pyonly parses flags and presents result paths. - 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.
- 4d ago First seen · 52 lines · 35 tokens per session scan A 4eb0fdc983d6
template-sia is a skill published in the GitHub repository docxology/template (19 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 494 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
launch-check
Run a pre-demo/pre-launch audit of the app - test data, broken screens, missing error states, brand consistency. Use when asked to 'demo check', 'launch check', 'pre-demo audit', 'check before user interview', 'audit before demo'.
cross-validation
The cross-validation skill enables the cross-validation agent to validate consistency between agent outputs and their sources. It provides the rules registry and validation runner that check pairwise consistency across the agent pipeline.
live-system-verification
Stands up a real running instance of the affected component(s) and runs testtype:live-system acceptance criteria against it — real HTTP calls, real process behavior, real evidence. Not a mock, not a simulated environment. Use when tasks.json contains any acceptance criterion tagged testtype: live-system.
lang-go
Go toolchain: golangci-lint, go vet, go test, go mod. CI gate commands, file layout, interface patterns. Use when working on a Go project.
lang-python
Python toolchain: ruff, mypy, pytest, pytest-cov, uv/pip. CI gate commands, file layout, pyproject.toml config. Use when working on a Python project.
performance-smoke-testing
Validate basic performance characteristics to detect regressions. Use when running lightweight load tests to measure latency, throughput, and error rates.