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-code-projectWrote 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-code-project)<a href="https://agentmods.dev/skills/docxology/template/template-code-project"><img src="https://agentmods.dev/badge/skills/docxology/template/template-code-project/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-code-project"><img src="https://agentmods.dev/badge/skills/docxology/template/template-code-project.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.00026 | $0.00490 |
| Opus 5.5 | $0.00010 | $0.00196 |
| Sonnet 5.5 | $0.00005 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
template-code-project 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.
This is a copy
78% identical to template-autoresearch-project — 25 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
template-code-project
Project-scoped skill for the in-repo exemplar at
projects/templates/template_code_project/. Load this when working inside the project.
When to Use
- Working inside the
template_code_projectexemplar — 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_code_project/tests --cov=projects/templates/template_code_project/src --cov-fail-under=90
uv run python scripts/pipeline/stage_02_analysis.py --project templates/template_code_project
uv run python scripts/pipeline/stage_03_render.py --project templates/template_code_project
uv run python scripts/pipeline/stage_04_validate.py --project templates/template_code_project
uv run python scripts/pipeline/stage_05_copy.py --project templates/template_code_project
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. - Keep tracked benchmarks deterministic. Serialize reproducible inputs, objective values, and checks; keep wall-clock timing as a runtime-only diagnostic.
- 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 · 54 lines · 26 tokens per session scan A f0971aad56fc
template-code-project is a skill published in the GitHub repository docxology/template (20 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 490 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 78% identical to template-autoresearch-project, differing in 25 lines, and is treated as a copy.
Other skills, from other repositories
pin-guardrail
Pin a shell guardrail (a hook, a git hook, a checker script) with a behavioral test suite, prove the suite is real by mutating the code, and wire it into CI with its mutation ledger. Use when asked to "add tests for this hook", "pin that guard", "mutation-test this script", "this hook has no test", "wire the suite…
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
review-ugc-render
Mandatory pre-publish review gate for a UGC video render. Transcribes the finished render's AUDIO with Whisper and word-diffs it against the approved spoken script, then gates keeping the render as the final version (videoreview) — blocking a render whose generated audio mis-voices a word (e.g. the approved…