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 agentmods add skills/docxology/template/code-developmentnpx skills add docxology/template --skill code-developmentgit clone --depth 1 https://github.com/docxology/templateWhat 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 | $0.00088 | $0.00684 |
| Opus 5 | $0.00044 | $0.00342 |
| Sonnet 5 | $0.00018 | $0.00137 |
| Haiku 4.5 | $0.00009 | $0.00068 |
Grade A, and why
template-code-development 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 yesterday.
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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code development
Natural invoke
- "Implement gradient descent in template_code_project src/"
- "Add a generic CSV validator in infrastructure/"
- "New analysis method with tests and logging"
Inputs to confirm
- Task — what to implement.
- Layer —
infrastructure(generic, 60% cov) vsproject(domain, 90% cov). - Project — if layer is project, from
docs/_generated/active_projects.md.
Workflow
-
Place logic correctly — computation in
infrastructure/orprojects/<n>/src/; scripts only orchestrate I/O and plotting. -
Implement — type hints on public APIs;
get_logger(__name__); custom exceptions extendingTemplateError; Google docstrings. -
Tests — real data, temp files, subprocess, or pytest-httpserver; no mocks (
docs/rules/testing_standards.md). -
Docs — update module/folder AGENTS.md + README.md when adding public surface.
-
Verify — ruff/mypy on touched paths; pytest with coverage gate.
Deliverables
- Module(s) with tests meeting coverage floor
- List of files touched and verification command output
Verification commands
uv run python -m infrastructure.project.public_scope lint-paths | xargs uv run ruff check
uv run python -m infrastructure.project.public_scope source-paths | xargs uv run mypy
uv run pytest projects/<project>/tests/ --cov=projects/<project>/src --cov-fail-under=90 -q
# or infra:
uv run pytest tests/infra_tests/ --cov=infrastructure --cov-fail-under=60 -q
When NOT to use
- End-to-end feature spanning manuscript + pipeline → feature-addition
- Tests only for existing code → test-creation
- New infrastructure package skeleton → infrastructure-module
References
docs/rules/— normative standardsdocs/core/architecture.md— two layers, thin orchestrator- Code patterns: references/patterns.md
What ships with it
5 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.
- yesterday First seen · 74 lines · 88 tokens per session scan A a6ed4f1842e4
template-code-development is a skill published in the GitHub repository docxology/template (19 stars, last pushed yesterday), licensed Apache-2.0. It adds 88 tokens to every session and 684 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
browser-trace
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page…
planning-with-files
Manus-style persistent file-based planning for AI coding agents: keeps taskplan.md, findings.md, and progress.md on disk so work survives context loss and /clear. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring 5+ tool calls. Supports automatic session…
ai-elements
Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface.
exa-search
Use Exa MCP for current web, code/docs, company, people, and page-fetch research. Prefer current hosted tool schemas and note deprecated tools.
ontoly-software-graph
Use Ontoly's deterministic Software Graph and MCP capabilities for repository architecture, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source search.
kimi-webbridge
Kimi WebBridge lets AI control the user's real browser — navigate, click, type, read, screenshot, and interact with any website using the user's actual login sessions. Use this skill whenever the user wants to interact with websites, automate browser tasks, scrape web content, or perform any action requiring a real…