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/decocms/studio/templatingnpx skills add decocms/studio --skill templatinggit clone --depth 1 https://github.com/decocms/studioWhat 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.00044 | $0.00697 |
| Opus 5 | $0.00022 | $0.00349 |
| Sonnet 5 | $0.00009 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
templating 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 2d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
templating — fill data into text-file templates
Render any text file (HTML, markdown, config, SQL, email, …) from a mustache template plus JSON data. Use this whenever the shape of an output is known ahead of time and only the values change — it is faster and less error-prone than writing the file by hand.
Other skills build on this one (e.g. slides composes presentation decks
from slide templates).
Quick reference
| Task | Command |
|---|---|
| Render with inline data | create-from-template --template t.html --data '{"name":"Ada"}' --output out.html |
| Render with a data file | create-from-template --template t.html --data @data.json --output out.html |
| Fail on missing keys | add --strict |
| Overwrite existing output | add -f |
Use partials ({{>name}}) |
add --partials-dir ./partials |
The command prints the absolute output path on success and exits non-zero
with a message on any error (bad JSON, missing template, existing output
without -f, missing keys under --strict).
Template syntax (mustache)
| Syntax | Meaning |
|---|---|
{{name}} |
Insert value, HTML-escaped |
{{{name}}} |
Insert value raw (no escaping) — for trusted HTML fragments |
{{#items}}…{{/items}} |
Repeat block for each array item; also renders for truthy values |
{{.}} |
The current item inside a list block |
{{^items}}…{{/items}} |
Render block only when the value is empty/falsy/missing |
{{user.name}} |
Dotted path lookup |
{{>header}} |
Include partial header (resolved from --partials-dir as header or header.html) |
{{!comment}} |
Comment, never rendered |
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.
- 2d ago First seen · 67 lines · 44 tokens per session scan A f4f34de58fbe
templating is a skill published in the GitHub repository decocms/studio (401 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 697 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-08-30.
Other skills, from other repositories
opengeni
Use when editing, operating, extending, documenting, or debugging the OpenGeni source repository or deployment: architecture, sessions/events, worker orchestration, sandbox backends, files/storage, tools/MCP, scheduling, configuration, and deployment. For a customer product that consumes a standalone OpenGeni…
refactor-module
Transform monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.
terraform-search-import
Discover existing cloud resources using Terraform Search queries and bulk import them into Terraform management. Use when bringing unmanaged infrastructure under Terraform control, auditing cloud resources, or migrating to IaC.
checkov
Use Checkov to scan Terraform and infrastructure-as-code repositories for policy violations, explain findings, choose safe fixes, rerun scans, and prepare pull requests with remediations.
document-parsing
Extract readable Markdown from local Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, and text-based PDF files using the preinstalled AnyDoc runtime.
opengeni-client
Use when an external product, coding agent, CLI, backend, or automation uses a standalone OpenGeni deployment through @opengeni/sdk or @opengeni/react. Covers choosing between a stock-UI handoff, a headless product integration, embedded React session surfaces, or the optional workbench; tenant-safe proxy boundaries…