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/sentdm/sent-plugin/template-builder-uinpx skills add sentdm/sent-plugin --skill template-builder-uigit clone --depth 1 https://github.com/sentdm/sent-pluginWhat 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.00054 | $0.01049 |
| Opus 5 | $0.00027 | $0.00524 |
| Sonnet 5 | $0.00011 | $0.00210 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
template-builder-ui 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sent Template Builder UI
Design the interface around Sent's v3 definition contract. The UI may import Meta material, but its canonical saved and submitted model must never be Meta's components[] payload.
Product model
Use one draft object with:
- optional
categoryandlanguage; - required
definition.body.multiChannel; - optional complete body overrides for
sms,whatsapp, andrcs; - optional
definition.header,footer,buttons,definitionVersion, andauthenticationConfig; - submission controls for
creation_source,submit_for_review, andsandbox.
Do not expose top-level create fields named name, channels, body, header, or buttons. If the product needs an internal display label, keep it outside the Sent create payload.
Recommended editor sequence
- Capture intent and category.
- Write the
multiChannelbody. - Insert variables as structured entities.
- Add optional per-channel overrides.
- Add header, footer, and buttons where supported.
- Review live previews and accessibility.
- Validate locally and with
sandbox: true. - Save a draft, then explicitly submit for provider review.
Category should not block the first keystroke, but it must be visible before submission because it affects authentication rules and WhatsApp policy review.
Variable UX
Inserting a variable creates both:
- a placeholder such as
{{0:variable}}; and - a matching entity with
id,name,type, andprops.sample.
Renumber atomically when variables move. Never let users edit placeholder syntax independently of the entity table. Show a clear error for naked {{1}} or IDs without definitions.
Validation matrix
Apply the exact rules in references/template-validation-matrix.md, including:
- a 1,024-character maximum for every body;
- 60 characters for header and footer;
- no footer variables;
- 10 buttons total;
- button types
QUICK_REPLY,URL,VOICE_CALL,PHONE_NUMBER, andCOPY_CODEwith their per-type limits; - no invented quick-reply-versus-CTA exclusivity;
authenticationConfigand authentication restrictions;- complete, independently valid channel overrides.
What ships with it
4 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 · 110 lines · 54 tokens per session scan A 1647a8cad3aa
template-builder-ui is a skill published in the GitHub repository sentdm/sent-plugin (52 stars, last pushed 23d ago), licensed MIT. It adds 54 tokens to every session and 1,049 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…