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-signing-requestnpx skills add ZapSign/api-mcp --skill create-signing-requestgit 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.00035 | $0.00480 |
| Opus 5 | $0.00017 | $0.00240 |
| Sonnet 5 | $0.00007 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
create-signing-request 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.
How it starts
The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a signing request
Use this skill when the user wants to send a PDF or DOCX for electronic signature without using a ZapSign template.
Required inputs
Collect:
- A document name.
- Exactly one source: a public HTTP(S) PDF URL, a public HTTP(S) DOCX URL, or raw base64 PDF content without a data URL prefix.
- At least one signer's full name.
Ask only for missing information that is required for the requested behavior. Email is required when automatic email delivery is enabled. phone_country without + and phone_number are required when automatic WhatsApp delivery is enabled.
Workflow
- Determine whether the user requested automatic email or WhatsApp delivery. Do not enable either channel by assumption.
- Build the signer list. Preserve the user's requested order. If signing order is requested, set
signature_order_activeand assign each signer anorder_group. - Before calling
create_document, summarize the document source, signer names, authentication methods, signing order, and automatic delivery channels. Ask for confirmation if the request will send a notification or create a signing request and the user has not already explicitly approved that exact action. - Call
create_documentexactly once with the confirmed values. - Report the returned document token and each signing link. State whether ZapSign was instructed to send email or WhatsApp notifications.
- If the tool returns an authentication error, ask the user to reconnect ZapSign. If validation fails, correct only the invalid input or ask for the missing value; do not invent contact information.
Rules
- Use
create_from_templateinstead when the user wants to fill dynamic fields in a reusable ZapSign template. - Never provide more than one document source in the same call.
- Never invent signer names, email addresses, phone numbers, tokens, URLs, or authentication methods.
- Treat returned signing links as sensitive. Show them only in the conversation where the user requested the signing workflow.
- Do not retry
create_documentafter an ambiguous timeout or unexpected error without checking whether a document was created 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 · 36 lines · 35 tokens per session scan A 0b33ec536136
create-signing-request is a skill published in the GitHub repository ZapSign/api-mcp (1 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 480 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-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.