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/zapsign/api-mcp/create-from-templatenpx skills add ZapSign/api-mcp --skill create-from-templategit clone --depth 1 https://github.com/ZapSign/api-mcpWhat 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.00027 | $0.00411 |
| Opus 5 | $0.00014 | $0.00205 |
| Sonnet 5 | $0.00005 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
create-from-template 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.
What it actually says
Create a document from a template
Use this skill when the user wants to generate a signing request from a reusable ZapSign DOCX template.
Workflow
- If the user did not provide a template token, call
list_templates. Present concise matches and ask the user to select one when the choice is ambiguous. - Call
get_templatefor the selected token before creation. - Read every
inputs[].variablereturned byget_template. Build thedataobject with those exact braced strings as keys, such as{{nome_completo}}. - Ask for the signer name and any missing template values. Do not rename variables, remove braces, or infer business-sensitive values.
- Enable automatic email or WhatsApp only when the user explicitly requests it and the corresponding contact value is present in the template data.
- Summarize the chosen template, signer, document name, populated variables, and delivery channels. Ask for confirmation if the user has not already explicitly approved creating that exact document or sending notifications.
- Call
create_from_templateexactly once. Includenameonly when the user requested a specific document name. - Report the returned document token and signing information. If the tool reports that creation succeeded but renaming failed, preserve the returned token and offer to call
update_documentwith that token.
Rules
- Never call
create_from_templatebeforeget_templateunless the user supplied the exact current variables and explicitly asks to proceed. - Never invent a template token, field value, signer identity, or contact value.
- Do not silently omit template variables. Explain which values are missing.
- Treat signing links and document tokens as sensitive.
- Do not retry creation after an ambiguous timeout or unexpected error without checking for the created document or asking the user, because creation is not idempotent.
What ships with it
1 file 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 · 28 lines · 27 tokens per session scan A 39c1da653e48
create-from-template is a skill published in the GitHub repository ZapSign/api-mcp (1 stars, last pushed 4d ago), licensed MIT. It adds 27 tokens to every session and 411 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.