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 skills add ActiveCampaign/postmark-skills --skill postmark-templatesgit clone --depth 1 https://github.com/ActiveCampaign/postmark-skillsWrote 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/activecampaign/postmark-skills/postmark-templates)<a href="https://agentmods.dev/skills/activecampaign/postmark-skills/postmark-templates"><img src="https://agentmods.dev/badge/skills/activecampaign/postmark-skills/postmark-templates/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/activecampaign/postmark-skills/postmark-templates"><img src="https://agentmods.dev/badge/skills/activecampaign/postmark-skills/postmark-templates.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.01337 |
| Opus 5 | $0.00018 | $0.00668 |
| Sonnet 5 | $0.00007 | $0.00267 |
| Haiku 4.5 | $0.00004 | $0.00134 |
Grade A, and why
postmark-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 9d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Templates with Postmark
Overview
Postmark templates are server-side email templates using Handlebars syntax. Templates are rendered on Postmark's servers — no client-side rendering library needed.
| Feature | Description |
|---|---|
| Syntax | Handlebars (Mustache-compatible) |
| Rendering | Server-side — no React, no client library |
| Types | Standard templates and Layout templates |
| Inheritance | Standard templates can inherit from a Layout |
| Validation | API endpoint to test-render templates before sending |
| Cross-server | Push templates between servers (staging → production) |
| Limit | 100 templates per server (contact support for more) |
Quick Start
- Create a template via API or the Postmark dashboard
- Define variables using Handlebars syntax:
{{variable_name}} - Send with template using
POST /email/withTemplateorPOST /email/batchWithTemplates - Pass data via
TemplateModel— Postmark renders and sends
Template Syntax (Handlebars)
Hello {{name}}, {{! variable }}
{{{html_content}}} {{! unescaped HTML }}
{{#if premium}}Premium member{{/if}} {{! conditional }}
{{#each items}}{{this.name}}{{/each}} {{! iteration }}
{{customer.address.city}} {{! nested object }}
See references/handlebars-syntax.md for the full syntax reference including conditionals, iteration with index, nested objects, and common mistakes.
Template Types
| Type | TemplateType |
Sendable | Purpose |
|---|---|---|---|
| Standard | "Standard" |
Yes | Defines subject, HTML, and text body |
| Layout | "Layout" |
No | Reusable wrapper injected via {{{@content}}} |
Standard templates can reference a Layout via LayoutTemplate: "layout-alias". The Standard template's body replaces {{{@content}}} in the Layout at send time.
What ships with it
3 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.
- 9d ago First seen · 138 lines · 37 tokens per session scan A cc0624a1f4a0
postmark-templates is a skill published in the GitHub repository ActiveCampaign/postmark-skills (45 stars, last pushed 21d ago), licensed MIT. It adds 37 tokens to every session and 1,337 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
architecture-patterns
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
agent-communication-protocol
Open protocol for AI agent interoperability enabling standardized communication between agents, applications, and humans across different frameworks.
design-code-architecture
Guided journey from an app idea to a deliberate architecture: boundaries, domain model, data decisions, and resilience, making only the expensive-to-reverse decisions and deferring the rest. Orchestrates eight skills phase by phase - clean-architecture, domain-driven-design, system-design, ddia-systems…
endpoint-validator
Deterministic API endpoint validation with pass/fail reporting.
measure-instrumentation-spec
Specifies what analytics events to track, when they fire, and what properties to include, as a contract between product and engineering that prevents undertracked features. Use before engineering builds a feature or when auditing existing tracking for gaps. For the dashboard built on top of these events, use…
api-patterns
API design: naming, versioning, pagination, idempotency, OpenAPI, error contracts and safe retries. Triggers: API design, REST, GraphQL, OpenAPI, Swagger, error response, HTTP status, rate limit.