templates

A command-line tool for managing reusable email messages with placeholders such as a recipient's name. It supports local templates and also describes hosted templates used by applications.

In plain words
What is it for?
Use it to list local templates, create or update messages with variables, render hosted templates with data, and send emails from a hosted template.
Why use it?
It avoids rewriting similar emails and makes it possible to fill in changing details consistently before sending.

Command

Install

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.

agentmods
npx agentmods add commands/nylas/cli/templates
Clone the repo
git clone --depth 1 https://github.com/nylas/cli
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,788 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02788
Opus 5 $0.00000 $0.01394
Sonnet 5 $0.00000 $0.00558
Haiku 4.5 $0.00000 $0.00279

Measured yesterday against content hash c7aa6e18401c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

templates 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.

docs/commands/templates.md · 402 lines

How it starts

The opening of the file, as written. The whole thing — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Email Templates

Manage locally-stored email templates for composing messages with variable substitution.

Templates are stored in ~/.config/nylas/templates.json and support {{variable}} syntax for placeholders. Variables are automatically extracted from the subject and body when templates are created or updated.

For API-backed hosted templates shared across an application or grant, use the top-level nylas template ... commands.


Hosted Templates Quick Reference

nylas template list
nylas template create --name "Welcome" --subject "Hello {{user.name}}" --body "<p>Hello {{user.name}}</p>"
nylas template render <template-id> --data '{"user":{"name":"Ada"}}'
nylas email send --to [email protected] --template-id <template-id> --template-data '{"user":{"name":"Ada"}}'

List Templates

nylas email templates list
nylas email templates list --category sales
nylas email templates list --json

Example output:

$ nylas email templates list

EMAIL TEMPLATES
Storage: /home/user/.config/nylas/templates.json

  tpl_170012345...  Welcome Email              Welcome {{name}}!                    onboarding (2 vars)
  tpl_170012346...  Sales Follow-up            Following up on {{topic}}            sales (3 vars) [used 5x]
  tpl_170012347...  Meeting Request            Request for meeting                  - (0 vars)

Total: 3 template(s)

Example with category filter:

$ nylas email templates list --category sales

EMAIL TEMPLATES
Category: sales
Storage: /home/user/.config/nylas/templates.json

  tpl_170012346...  Sales Follow-up            Following up on {{topic}}            sales (3 vars) [used 5x]

Total: 1 template(s)

Available flags:

  • --category, -c - Filter templates by category
  • --json - Output as JSON
  • --quiet, -q - Only output template IDs

Show Template

nylas email templates show <template-id>
nylas email templates show <template-id> --json

Example output:

$ nylas email templates show tpl_1700123456789

────────────────────────────────────────────────────────────
Template: Welcome Email
────────────────────────────────────────────────────────────
ID:         tpl_1700123456789
Name:       Welcome Email
Category:   onboarding
Created:    Jan 15, 2026 10:30 AM
Updated:    Jan 20, 2026 2:45 PM
Used:       12 time(s)
Variables:  name, company

Subject:
  Welcome to {{company}}, {{name}}!

Body:
  Hi {{name}},

  Welcome to {{company}}! We're excited to have you on board.

  Best regards,
  The Team

────────────────────────────────────────────────────────────
Usage:
  nylas email templates use tpl_1700123456789 --to <email> --var name=<value> --var company=<value>

Read the full file on GitHub · 402 lines

Changes

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.

  1. yesterday First seen · 402 lines · 0 tokens per session scan A c7aa6e18401c

Subscribe to this mod's changes

templates is a command published in the GitHub repository nylas/cli (68 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,788 tokens. 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.